Run terminal-native coding agent workflows with GitHub Copilot CLI
Use GitHub Copilot CLI to plan, edit, debug, explain, and automate repository work from a terminal with GitHub context and approval controls.
npx skills add agentskillexchange/skills --skill run-terminal-native-coding-agent-workflows-with-github-copilot-cli
Use GitHub Copilot CLI when a developer or operator wants Copilot coding-agent work to happen synchronously in a local terminal with repository, issue, pull request, MCP, and shell context. The operator installs the CLI, authenticates with a Copilot-enabled GitHub account or token, launches it inside a repository, asks for a bounded coding or debugging task, previews proposed actions, and approves only the commands or edits that should run. Inputs are the local repo, prompt, GitHub authentication, optional MCP servers, selected model, and approval mode. Outputs are code edits, explanations, debug findings, command results, GitHub-context answers, and reviewable terminal history. The scope boundary is terminal-native supervised coding-agent operation with GitHub context, not a generic Copilot product card, IDE extension, SDK, or hosted coding assistant listing.
What this skill actually does
Inputs and prerequisites: GitHub Copilot CLI, active GitHub Copilot subscription, GitHub authentication or PAT, local repository, terminal, and optional MCP servers.
Setup notes: Install with the official GitHub Copilot CLI installer, Homebrew, WinGet, or npm package @github/copilot. Launch copilot inside a repository, authenticate with GitHub or a token with Copilot Requests permission, choose a model if needed, then run supervised coding, debugging, explanation, and GitHub-context tasks from the terminal.
Source and verification boundary: use https://docs.github.com/copilot/concepts/agents/about-copilot-cli as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Custom Agents workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.