docs: add /research slash command to course content#6
Conversation
Integrate the /research command across three chapters: - Ch 01: Add to essential and additional slash command tables - Ch 03: Add 'Quick Tip: Research Before You Code' section with example and link in Choose Your Own Adventure table - Ch 07: Use /research in Bug Investigation workflow (Phase 2, before switching to an agent) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds documentation for the /research slash command across the course so learners see it early, understand when to use it, and see it applied in an end-to-end workflow.
Changes:
- Chapter 01: Adds
/researchto the Essential Slash Commands list and the Additional Commands “Code” table. - Chapter 03: Adds a “Quick Tip” section demonstrating
/research(and positioning it before/plan), plus a new entry in the chapter’s navigation table. - Chapter 07: Updates the bug investigation workflow phases to use
/researchearlier (before switching to an agent).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| 01-setup-and-first-steps/README.md | Documents /research in the starter command tables. |
| 03-development-workflows/README.md | Adds a quick-tip section + navigation link showing the /research → /plan pattern. |
| 07-putting-it-together/README.md | Incorporates /research into the end-to-end bug investigation workflow phases. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | `/plan` | Plan your work out before coding | For more complex features | | ||
| | `/research` | Deep research using GitHub and web sources | When you need to investigate a topic before coding | | ||
| | `/model` | Show or switch AI model | When you want to change the AI model | |
There was a problem hiding this comment.
The surrounding text now conflicts with the table: it says “Start with just these four”, but adding /research makes the list longer (and the “five commands above” note in the Additional Commands section is also now off-by-one). Please update the counts/wording so the guidance matches the table contents.
| # Learn: "find_by_author doesn't work with partial names" | ||
|
|
||
| # PHASE 2: Find related code | ||
| # PHASE 2: Research best practice (deep research with web + GitHub sources) |
There was a problem hiding this comment.
Minor grammar: “Research best practice” reads awkwardly in this context; “best practices” is more standard when referring to general guidance.
| # PHASE 2: Research best practice (deep research with web + GitHub sources) | |
| # PHASE 2: Research best practices (deep research with web + GitHub sources) |
Summary
Integrates the
/researchslash command across three chapters of the course. The additions are concise — a command table entry, a quick tip section, and a workflow example.Changes
Chapter 01 (First Steps)
/researchto the Essential Slash Commands table/researchto the Additional Commands > Code reference tableChapter 03 (Development Workflows)
/research→/planpatternChapter 07 (Putting It All Together)
/researchin Phase 2 (before switching into an agent), showing it naturally in an end-to-end workflowWhy this placement
/help,/plan,/clear/researchbefore/agentin the bug fix flow shows the real-world pattern: research first, then bring in specialists