Inputs
- A pinned repository commit
- A reproducible issue
- Acceptance criteria
- Allowed commands and file scope
Control points
- Isolated branch or worktree
- No secret access
- Baseline and post-change tests
- Protected merge path
Human approval gate
A repository maintainer approves the diff, test evidence, dependencies, security impact, and issue acceptance before merge.
The workflow
Every step includes a check that can stop the process before risk moves downstream.
- 01
Reproduce before editing
Run the stated reproduction and record environment, baseline output, and existing failures.
Gate: The issue is observable or the task stops for clarification. - 02
Propose the smallest change
Identify affected files, behavioral risk, tests, and anything explicitly out of scope.
Gate: A maintainer can reject scope expansion before code changes. - 03
Implement in isolation
Make the patch without changing unrelated files, credentials, or deployment state.
Gate: Unexpected changes block the workflow. - 04
Run relevant checks
Execute targeted and broader tests, type checks, lint, and security checks that apply.
Gate: Every passing claim links to command output; skipped checks are explained. - 05
Review and merge normally
Inspect correctness, tests, readability, dependencies, and rollback under normal branch protection.
Gate: Human approval and repository policy remain mandatory.
Candidates to pilot
Inclusion means relevant product shape, not measured superiority.
Sources checked
Open the original pages before relying on a time-sensitive product decision.