Agent WranglersReviewing agent output
A person reads every change an agent makes, runs it, and checks for invented packages, weakened checks and changes outside the task before it ships.
- Required 5
- Recommended 2
Required
Read every line of the diff
RequiredA person reads every line an agent changes before it merges, and can explain why each line is there.
Run the change yourself
RequiredRun the changed feature by hand before approving it, and never trust an agent's claim that it works.
Check that every package and API exists
RequiredVerify every new dependency and every called API exists, is the official one and does what the code assumes.
Look for weakened checks and skipped work
RequiredReject any change that deletes or skips tests, loosens a linter or type setting, or catches and hides errors to make the checks pass.
Check the change does only what was asked
RequiredReject changes that touch files, features or behaviour the task did not ask for.
Recommended
Get a fresh review for risky changes
RecommendedFor changes to money, accounts, permissions or data deletion, get a second review from someone, or an agent, that did not write the change.
Check where generated code came from
RecommendedMake sure generated code does not copy licensed code you may not use, and that every new dependency's licence fits your project.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers ai development playbook: https://agentwranglers.se/playbook/ai-assisted-development/reviewing-agent-output.