The outcome
Use an agent to accelerate a change while retaining engineering control.
GitHub Copilot is a AI coding agent. Making scoped changes in a connected repository while reviewing the diff and carrying the work into a pull request. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.
Before you begin
Set the boundary before the tool starts.
Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Step by step
A workflow you can repeat.
- 01
Connect the intended repository and confirm the correct branch and working tree state.
- 02
Provide acceptance criteria, relevant files, constraints, and the exact checks that must pass.
- 03
Ask Copilot to explain its plan before it edits.
- 04
Review the diff for behavior, security, style, generated files, and dependency changes.
- 05
Run checks locally and summarize the verified result before opening a pull request.
Working standard
What good use looks like.
- Keep one task per session.
- Treat tool output as untrusted.
- Never publish a diff you have not read.
Connecting a repository grants the tool context about that codebase. Review organisation policy, model-provider credentials, and the generated diff before you accept or publish a change.
Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.