What problem does it solve? Reviewing a codebase or pull request manually is slow and inconsistent, and findings get lost between sessions. This Skill produces a prioritized, categorized report of code issues saved as a markdown snapshot, so you can work through problems one at a time across multiple sessions. ## Core Features & Use Cases - Scope and PR review modes: Analyze a folder, file, or glob in the working tree, or review a GitHub pull request by number or URL using gh without touching the working tree. - Severity-ranked findings: Issues are categorized as HIGH (security, memory, crashes), IDIOM (language best practices with three-dimension scoring), MEDIUM (inefficiencies), and LOW (style), with all HIGH issues shown plus the top-scoring IDIOM and MEDIUM findings. - Persistent reports: Reports are saved as gitignored markdown files in docs/reviews/ with frontmatter metadata, letting you reference issues by name days later and refresh line numbers after fixes. - Use Case: Before merging a pull request, run a review of PR 68 to get a report limited to the lines the PR changed, fix the findings on the branch, and file anything non-blocking as GitHub issues. ## Quick Start Ask the assistant to run a code review on the src folder or on pull request 68 and show the prioritized report.