What problem does it solve? Self-reviewing your own code changes is easy to skip or do superficially, and generic review feedback often ignores the specific conventions and architectural boundaries of the repository you are working in. This Skill reviews your diff against the repository's actual rules documents and returns prioritized, evidence-backed findings without posting anything to GitHub. ## Core Features & Use Cases - Convention-grounded review: Locates and reads the repository's own rules (CLAUDE.md, .claude/rules/, docs/, lint configs) and cites them as the basis for findings instead of relying on memory. - Three-tier severity: Classifies every finding as must (merge blocker), imo (improvement suggestion), or nits (trivial), with mandatory verification before anything is raised to must. - Scoped diff analysis: Defaults to the three-dot range origin/HEAD...HEAD, excludes generated files, lockfiles, and vendored code, and defers comment-style and test-coverage concerns to dedicated sibling skills. - Use Case: Before opening a pull request, ask for a self-review of your branch. The Skill reads the repo's conventions, checks boundary violations, complexity, and failure scenarios, and returns a structured report with a fix checklist. ## Quick Start Review my current branch changes against this repository's conventions and give me must, imo, and nits feedback.
