AI coding tools

GitHub Copilot Operating Card

Use GitHub Copilot chat, coding agent, CLI, and code review with repository instructions, branch protection, and human validation.

Core concept
CurrentNext review due 2026-08-25Content version 0.36.0
Format
Reference
Level
Beginner
Audience
Practitioner, Developer, Operator
Owner
Project42 Editorial
Review cadence
Every 30 days
Prerequisites
An approved GitHub Copilot plan and policy; A version-controlled repository; Repository review and branch controls
01

Match the Copilot surface to the task

GitHub Copilot includes interactive editor and CLI assistance, cloud coding-agent workflows, and code review. Use interactive surfaces for close collaboration, coding agent for bounded branch work, and code review as supplemental feedback.

Copilot review can miss problems or make mistakes. Preserve required human review, automated checks, branch protections, and accountable release approval.

02

Provide shared repository instructions

Use AGENTS.md for cross-tool rules and Copilot-specific or path-specific instruction files only where their scope is intentional. Include build, test, architecture, and security expectations that can be verified.

Review requested CLI commands, agent session activity, pull-request changes, and review suggestions. Treat MCP servers and skills as separately governed dependencies.

GitHub Copilot task card
text
Task: [issue or one bounded result]
Scope: [repository, branch, and paths]
Permissions: [agent, CLI, MCP, network, and repo access]
Instructions: [AGENTS.md and Copilot-specific rules]
Expected output: [diff, PR, review, or report]
Verification: [checks plus accountable human review]
Recovery: [stop session, close PR, revert branch, reconcile]
03

Expected evidence and verification

Expected evidence includes the issue or prompt, instruction files used, commands or session log, pull-request diff, automated checks, and human disposition of review findings.

If Copilot changes the wrong scope or gives unsafe feedback, stop the workflow, preserve the evidence, restore the branch or files, and refine the issue and instruction boundary before retrying.