What problem does it solve? Static analysis tools miss semantic defects like logic errors, race conditions, and requirement mismatches. This Skill provides a read-only review protocol that catches those issues and classifies every finding by severity before merge. ## Core Features & Use Cases - Four review dimensions: logic and correctness, design quality, security patterns (injection, credential exposure, path traversal), and requirement fidelity. - Severity classification: every finding is labeled Critical, Error, Warning, or Info, with a final verdict of PASS, PASS_WITH_WARNINGS, NEEDS_CHANGES, or PRECONDITION_FAILURE. - Ground-truth enforcement: refuses to review from memory; emits PRECONDITION_FAILURE when the cited source path is missing or unreadable. - Use Case: A subagent receives a pull request diff, verifies the source path exists, reads every changed file plus surrounding context, and returns a findings table with file:line references and a merge verdict. ## Quick Start Ask the code-review-expert subagent to review the diff in the current branch against main and return a structured findings table with a verdict.
