A good fit for
- → Terminal-native development
- → Small, reviewable patches
- → Comparing model behavior within one Git workflow
Know the limits
- → Model capability still determines edit quality.
- → Excessive context can distract the model and increase cost.
- → The selected provider may receive repository content.
Your first useful workflow
Create a clean branch
Start from a known commit and run the existing tests.
Select relevant files
Add likely edit targets and only the supporting context needed for the task.
Inspect changes
Review generated commits and run checks rather than accepting the explanation alone.
The practical take
A small, relevant edit context often beats attaching the entire repository.
Sources & evidence
Capabilities above are summarized from these official documents. Workflow suggestions are editorial guidance, not a claim of measured product superiority.