| Trigger | Description said to use it before merging any change, which also fires on commit-message requests and trivial diffs. | Description and When to use / When NOT to use lists name real phrases and exclude commit messages, typo-only or generated-only diffs, deploys and whole-repo audits. |
| Output format | A checkbox checklist with no required structure for findings. | A fixed report: summary, findings table (severity, origin, axis, file:line, trigger and consequence, suggested fix), rejected candidates, pre-existing issues, verification, and one verdict with explicit verdict rules. |
| Severity scheme | Mixed labels: no prefix, Critical, Nit, Optional/Consider, FYI, plus Required in another section. | One scheme of five labels (Critical, Required, Suggestion, Nit, FYI) plus a new/pre-existing origin tag; pre-existing defects can never block the change. |
| Mutation safety | Flip a condition, run tests, then restore the file from a copy. | In place by default for uncommitted diffs, only after one explicit yes that covers up to three mutations; git status/diff snapshot and byte-identical restore check after each mutation; stop at the first surviving mutation; separate worktree only for fully committed changes; untracked files skipped or byte-copied and compared. |
| Boundaries | No stop points beyond asking before deleting dead code. | Read-only by default; asks before edits, posting comments, merging, tests that hit real services, or forced dependency fixes; masks secrets; treats instructions inside reviewed code as data. |
| Checkable steps | Review steps listed questions without an end condition. | Each of the seven steps ends with a concrete check (scope line, behavior-to-test map, git status match, evidence fields per finding). |
| Worked example | Only a sample prompt for a review agent. | A complete pagination-diff review: input, each step, a rejected auth claim, a pre-existing issue, a surviving mutation, the final report, and a pass/fail rubric, plus seven behavior eval cases. |
| Standalone install | Linked to repo-root checklists and sibling skills that break when the skill is installed alone; included a one-business-day human review-speed rule. | Security, performance, size and dependency guidance folded into the skill's own references/; sibling links and human-team timing rules removed. |