A developer in the terminal needs two things in quick succession: a one-off shell command to count lines across the repository, and then a prose walk-through of how an existing build script's logic works. Which use of the GitHub Copilot CLI matches both needs within the same tool?
- ARequest the count command from the CLI, then use editor inline completions for the script walk-through, because the CLI cannot describe an existing script's behaviour.
- BOpen Copilot code review for the count command and Copilot Spaces for the script explanation, because neither task is something the terminal CLI is built to do.
- CUse the CLI to suggest the count command, then ask the CLI to explain the build script, since the CLI handles both command generation and command explanation. Correct
- DAsk the CLI for the count command, but switch to editor Agent Mode for the script explanation, as the CLI only generates commands and never explains them.
Why A is wrong: This wrongly limits the CLI; it can both suggest a command and explain an existing command or script, so no handoff to inline completions is needed.
Why B is wrong: This misroutes both tasks; code review acts on pull request diffs and Spaces curates context, while the CLI is the surface built for terminal command work.
Why C is correct: The GitHub Copilot CLI supports both generating a command from a description and explaining an existing command or script, covering both needs in one tool.
Why D is wrong: This is tempting but inaccurate; the CLI does explain commands and scripts in plain English, so switching to Agent Mode for the walk-through is unnecessary.