Code review

When agents write the code, the number of changes goes up fast, and manual, line-by-line review becomes incredibly difficult if not impossible. Review still does two jobs: find and fix issues before they ship, and build shared context across the team. "Did a human read the code?" is an imprecise proxy for "what could go wrong with this change, and which check, automated or human, is the right one to catch it?" Most of the reading moves to machines, human time goes where the risk is, and mistakes are made fast and easy to undo. What to look for inside one diff (slop, defenses in the wrong places, should it exist, the per-file verdict table) is anti-slop-code; whether the tests can catch a bug is testing.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]