01The suite
A pen per requirement.
Turn code review into regression tests.
Use approved review comments as requirements to test each prompt, model and tool change against.
01The suite
A pen per requirement.
38Requirements from review comments
WEEK 12 · 37 OF 38 HELD
- 01
A reviewer’s comment becomes a requirement.
- 02
Your repository owner approves it.
- 03
Prompt rev 7, tool v2.3. Every trace holds.
- 04
The model update drops the lockfile. Spike.
- 05
The spike points back to one comment.
- Docs-only changesOwn
- Dependency bumpsReview
- Schema migrationsReview
- Production configurationDo Not Delegate
- New monorepo changesInsufficient Evidence
- REQ-31 · Lockfile in the same commit · from #4131.
- REPO OWNER · APPROVED.
- Prompt rev 7, Tool v2.3: 38 of 38 held.
- Model update: REQ-31 spikes, 37 of 38 held. SELF · RECOMMENDS REVIEW, REPO OWNER · APPROVED, BRANCH PROTECTION · ENFORCES.
- #4131 · review comment: “Put the lockfile in the same commit.”
02How it fits
- 01
Signals in
Each pull request, the reviewer’s decision on it, and what shipped.
- 02
Recommendation out
Handling for each class of work, with the evidence behind it.
- 03
Enforcement stays yours
Branch protection applies it. Self never acts in your repository.