Red team review

Target and oracle

Settle both before the missions start, in two lines the user can correct:

• Target: the document path, or the branch, the base and the exact commit hash. The review covers that hash only. Commits added later are not reviewed, and the report says so.
• Oracle: what the change must keep or reach. For a refactor or any change that promises "no behavior change", the oracle is the base branch: the same input must give the same responses, rows, events and messages. For a feature, it is the spec and its acceptance criteria. For a spec or a plan, it is the request and the code it will touch.

Facts first

Some checks are deterministic: a tool gives the same answer every time and costs no agent turns. Examples are mutation testing (the proof that the tests kill a broken line), the test suite run on the base, linters and static analysis, dependency audits, secret scans, architecture tests, a diff of routes or commands, a merge of the other active branches with the test suite. They are facts, not missions.

• Run only the checks that the user gives or that an add adjustment of this skill names (customize-yak), with the exact command, scoped to the changed code. Never search the project for such a tool and launch it on your own. A mutation run over a whole repository takes hours.
• Give their output to the missions. A mission judges that output; it does not run the check again or imitate it by hand.
• A check that nobody configured goes under "Not covered", with the tool you would use and the adjustment that would add it.

Missions