code-reviewer

# Code Reviewer ## Overview This skill performs a thorough, structured code review of a change set (a diff, a pull request, staged changes, or a list of modified files). It surfaces **correctness bugs**, **security vulnerabilities**, and **quality/maintainability** issues, ranks every finding by severity, and gives an actionable fix for each one. Keywords: code review, PR review, diff review, bug hunting, security review, pull request, merge readiness, static review, defect detection. The review is **diff-scoped by default**: focus on what changed and what the change touches. Do not rewrite the whole codebase. The deliverable is a review report, not a refactor. ## When To Use - User says "review this PR / diff / branch / changes". - User pastes a patch, unified diff, or set of files and asks for feedback. - Before a merge, when the user wants a gate check. - After implementing a feature, to self-review prior to opening a PR. ## Workflow Follow these steps in order. ### 1. Gather the change set Determine exactly what to review. Prefer the narrowest accurate scope. - GitHub PR: `gh pr diff <number>` (or `gh pr view <number> --json files,title,body`). - Local branch vs base: `git diff <base>...HEAD` (three-dot = changes on the branch since it forked). - Staged: `git diff --staged`. Unstaged: `git diff`. - A given commit: `git show <sha>`. - If only file paths are given, read those files and, where needed, the symbols they call. Capture: changed files, hunks, the PR ti...