A guide to slash commands in the GitHub Copilot app
GitHub’s Copilot app now supports slash commands to streamline workflows, offering shortcuts for planning, collaboration, automation, and customization within the visual interface.
The useful question is what changes for users, developers or buyers, and whether the announcement stays industry context or becomes something people can actually use.
GitHub has introduced slash commands in its Copilot app to provide quick shortcuts for managing sessions, navigating projects, and customizing workflows. Typing a forward slash (/) triggers an autocomplete menu that displays available commands based on the current context, enabling faster interactions without leaving the chat interface. Unlike the CLI version, these commands focus on workflow efficiency rather than terminal-specific tasks, as the app automatically handles project context such as file access.
The /plan command helps developers break down tasks by outlining approaches, identifying challenges, and organizing next steps before coding begins. It also switches the session into Plan mode, allowing users to systematically structure their work. The /spar command acts as a critical reviewer, prompting Copilot to challenge assumptions and highlight potential risks or tradeoffs, ensuring thorough validation of ideas before implementation.
For implementation, the /autopilot command guides Copilot through coding tasks, allowing it to iterate and make changes autonomously while switching the session into Autopilot mode. The /rubber-duck command provides an independent review by using a different model to surface blind spots, question assumptions, and catch issues, particularly useful for complex refactors or architectural decisions where a second opinion is valuable.
Additional commands like /create-canvas transform chat-based discussions into interactive visualizations such as dashboards or workflows, while /orchestrate coordinates work across multiple repositories or sessions. Users can explore commands via autocomplete and gradually adopt those that align with their workflow, with documentation available for further guidance.