oldhand-review

Reviews a code change with a board of read-only reviewer sub-agents, one lens each (contract, correctness, security and simplicity, plus data and AI behaviour when the change touches them). Each reviewer reads a stand-alone brief and writes a memo of file:line findings with failure scenarios; the chair tries to refute every finding before accepting it, records survivors in the Oldhand ledger, fixes high and medium findings, and lists lows as follow-ups. One review round and one fix round. Writes review.md and a review folder in the task's .oldhand folder. Use when the user says "review this", "review my diff", "review the PR", "find bugs in this change", "adversarial review", "get a second opinion on this code", or after oldhand-build. Not for style-only feedback, auditing a whole codebase, or explaining code. One stage of oldhand; for a whole ticket or fix, use oldhand.

License

MIT