Review Boundary
The review covers source diff, related tests, command evidence, scope control, regression risks, and handoff instructions. It does not replace repository owner review or CI.
Scorecard
| Area | Rating | Evidence To Check | Notes |
|---|---|---|---|
| Acceptance criteria coverage | 4 / 5 | Requested behavior has implementation and tests. | Paid review maps each criterion to files and checks. |
| Scope control | 5 / 5 | Diff touches only required files. | Important for AI patches where unrelated churn is common. |
| Test evidence | 3 / 5 | Targeted tests pass; broader integration checks may be needed. | Paid review cites exact commands and output. |
| Regression risk | Medium | Shared parser, config mutation, file writes. | Needs negative cases and clean-base verification. |
| Maintainer handoff | 4 / 5 | Branch, commit, patch, apply commands, verification commands. | Strong fallback when push/PR permissions fail. |
Recommended Decision
Proceed to maintainer review if targeted tests pass on a clean checkout and the patch applies against the correct base branch. Run normal CI before merge.
$100 First Slice
- Acceptance-criteria coverage table
- Exact files and commands reviewed
- Test command plan and observed results
- Regression-risk list and missing edge cases
- Maintainer-ready handoff message
- Approve / revise / reject recommendation
Inputs Needed
- Repository URL or patch bundle.
- Original task or acceptance criteria.
- Preferred base branch.
- Commands that count as proof.
- Files or behavior that must not be touched.