Code Review

This is a Hermes-native code-review workflow skill.

Why This Exists

code-review exists to make review bug-first and evidence-grounded: findings must cite concrete files, diffs, commands, or artifacts before any summary or fix proposal.

Do Not Use When

• The user asks to implement the fix rather than review existing code or claims.
• There is no diff, file set, claim, artifact, or expected behavior to review.
• The request is broad product critique, strategy, or planning rather than code or evidence review.
• The user wants build, lint, test, and CI results collected into a PASS/HOLD/BLOCK evidence matrix before merge; use omh-verification-gate. This skill supplies findings that matrix may cite.
• A kanban review worker needs its card's transition decided: Hermes' bundled sdlc-review owns approve, request-changes, and escalate there, and this skill only supplies the findings that decision cites.
• The user wants their own uncommitted changes checked before a commit or push, with a security scan, quality gates, and fixes applied in place; load Hermes' bundled requesting-code-review skill for that pre-commit pass instead of this one.

Examples