Coding-agent reviewer
Solo builders and small teams reviewing agent-written diffs. · Turn agent output into an auditable PR packet before it reaches production.
Before you start
- Comfortable with git and pull requests
- Familiar with code review practices
0%0/4 steps
Path artifact
A pull-request packet with intent, diff map, tests, risks, and rollback.
Finish every lesson and you should have: A pull-request packet with intent, diff map, tests, risks, and rollback..
Write what must change, what must not, and the files likely in scope.
Pitfall
Letting the agent discover scope by editing.Verification
The final diff can be judged against the original intent.Ask the coding agent for the narrow change and ban unrelated cleanup.
Pitfall
Accepting architectural polish as progress.Verification
Every changed file maps to the intent lock.Use a second model to list regressions, security issues, and accessibility breaks from the diff.
Pitfall
Asking for reassurance instead of failure modes.Verification
At least one plausible failure path is tested or dismissed.Run relevant checks and write what passed, failed, or was not checked.
Pitfall
Mistaking typecheck success for product confidence.Verification
The PR note includes concrete validation output.You should now have: A pull-request packet with intent, diff map, tests, risks, and rollback..
- The final diff can be judged against the original intent.
- Every changed file maps to the intent lock.
- At least one plausible failure path is tested or dismissed.
- The PR note includes concrete validation output.