Review recipes
Full repository audit
- Run
scripts/audit_agent_use.py --root <repo> --markdown --output agent-use-report.md --json-output agent-use-report.json. - Run
scripts/action_parity_inventory.py <repo> --output action-parity-inventory.md --csv-output capability-map.csvfor app/tool repos. - Inspect the generated capability map and manually classify high-value workflows.
- Open the main routes/controllers/tools/CLI commands and verify implementation-level evidence.
- Score only applicable dimensions and produce a prioritized plan.
Pull request review
- Identify changed user actions, tool/API/CLI surfaces, prompts, auth/safety code, and docs.
- Ask whether each new human action has an agent path and each new agent path has context, safety, and verification.
- Do not require full parity for unrelated old code unless the PR worsens it.
- Recommend small patches: schema field, JSON output flag, dry-run option, docs link, eval, or capability-map row.
Parallel review
For a large product, split reviewers by principle:
- Action parity.
- Context parity.
- Tool/API/CLI contract quality.
- Safety/permissions/recovery.
- Web/docs discovery.
- Evals/observability.
Merge by capability map, not by file list, so duplicate findings collapse into user-visible workflows.
Acceptance tests for fixes
A fix is done when a fresh agent can discover the surface, choose the right action, provide required context/credentials, execute or preview safely, parse output, verify final state, and recover from one common error.