Use GitHub Copilot slash commands to structure agent sessions
GitHub's slash-command guide is a practical reference for planning, challenging, automating, and reviewing work inside the Copilot app.
- LinkLoot access
- Free
- Provider costs
- Unknown
What you get from it
Practical testing not documented.
LinkLoot assessment · not a user rating.
GitHub's new Copilot app slash-command guide is useful when a team already uses Copilot but still treats every agent session like an open-ended chat. The commands turn common workflow moves into explicit actions: plan the work, challenge an approach, hand off implementation, ask a second model to review, or turn a conversation into a canvas.
What it is
The guide explains slash commands in the GitHub Copilot app. Commands such as /plan, /spar, /autopilot, /rubber-duck, and /create-canvas map to common agent workflows rather than generic chat prompts.
Who it helps
It helps developers, tech leads, and reviewers who want more predictable coding-agent sessions. It is most useful for teams that already use the Copilot app and need a shared vocabulary for planning, implementation, risk review, and handoff.
How to evaluate it
Start by trying /plan on a small bug or refactor, then compare the resulting plan with your normal issue checklist. Use /spar for architecture tradeoffs, /autopilot only on scoped tasks with tests, and /rubber-duck before opening a pull request for larger changes.
Limits and risks
The commands do not replace review, testing, or repository policy. /autopilot can still make broad changes if the task is vague, and second-opinion commands can miss project-specific constraints. Teams should pair these shortcuts with branch protection, CI, and human review for production code.
Sources
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in