Copilot CLI: Prompting, Interactive Use, and Core Workflows

copilot -p "Summarize what this file does: ./README.md"

# Run Copilot non-interactively with a prompt.

copilot -p "Explain this file: ./complex.ts"

# Ask Copilot to explain a code file directly from the terminal.

echo "Explain this file: ./complex.ts" | copilot

# Send prompt text over stdin.

copilot -p "In Git, how can I apply a commit from another branch"

# Get a concise terminal answer about a shell task.

copilot -p "Plan a safe refactor of this module and list the files you would inspect first."

# Use Copilot to plan work before making changes.

copilot -p "Summarize the intent of the last 10 commits in this repository."

# Use Git context from the repo in a direct prompt.

@ README.md

# Reference a file inline inside the interactive UI.

! git status

# Execute a local shell command directly from the session.

Ctrl+G

# Open the current prompt in your configured editor.

Ctrl+L

# Reset visual clutter during long sessions.

Esc

# Stop the current task or prompt execution.

Ctrl+D

# Shut down the session from the keyboard.

copilot -p "A test is failing after the last merge. Inspect the codebase, identify the likely cause, and propose the smallest safe fix."

# Describe the failure and let Copilot inspect the repo.

copilot -p "Add a health check endpoint to this app and explain which files need to change."

# Ask for a small feature implementation plan and changes.

copilot -p "Document the public API and side effects of this module in concise Markdown."

# Ask Copilot to document unfamiliar code.

copilot -p "Review the changes in this working tree and flag risky edits or missing tests."

# Ask for a human-readable review of local modifications.

copilot -p "Give me a quick onboarding guide to this repository: main entry points, architecture, setup commands, and important directories."

# Ask Copilot for an architecture tour.