~/.claude/skills/pr-reviewer/SKILL.mdPR Reviewer
Reviews code changes like a senior developer: checks logic, security, performance, naming, and suggests improvements with explanations.
--- name: pr-reviewer description: | Reviews pull requests and code changes like a senior developer. IMPORTANT: Activate this skill whenever the user asks to "review this PR", "review my changes", "code review", or "check my code". This skill MUST be used for all code review requests. --- # PR Reviewer Reviews code changes with the eye of a senior developer. Checks for logic errors, security issues, performance problems, naming clarity, and suggests concrete improvements with explanations. **Trigger:** Say any of these to activate this skill: - "review this PR" - "review my changes" - "code review" - "Use skill: pr reviewer" **How It Works:** 1. Read the diff (staged changes, PR diff, or specified files) 2. For each changed file, understand the context by reading surrounding code 3. Check for: logic errors, missing edge cases, security vulnerabilities, performance issues 4. Check naming clarity: do variable/function names describe what they do? 5. Check for consistency with the project's existing patterns 6. Categorize findings by severity: critical (must fix), suggestion (should fix), nit (optional) 7. For each finding, explain WHY it's an issue and suggest a specific fix 8. Summarize: overall assessment, critical issues count, suggestions count **Guidelines:** - Focus on bugs and security first, style and naming second - Every criticism must include a suggested fix (not just "this is wrong") - Do not nitpick formatting if the project has a formatter (Prettier, ESLint) - Acknowledge what's done well, not just what's wrong - Be specific: "Line 42: this null check misses the empty string case" not "check your inputs" **Works With:** - Best with: Claude Code CLI (can read git diff and full file context) - Also works: Cursor, Windsurf, any AI tool (paste the diff) - Expects: A git repository with staged or committed changes to review **Output Format:** - Summary: one-paragraph overall assessment - Findings list: severity, file:line, description, suggested fix - Verdict: approve, request changes, or needs discussion
Reviews code changes with the eye of a senior developer. Checks for logic errors, security issues, performance problems, naming clarity, and suggests concrete improvements with explanations.
Say any of these to activate this skill: - "review this PR" - "review my changes" - "code review" - "Use skill: pr reviewer"
1. Read the diff (staged changes, PR diff, or specified files) 2. For each changed file, understand the context by reading surrounding code 3. Check for: logic errors, missing edge cases, security vulnerabilities, performance issues 4. Check naming clarity: do variable/function names describe what they do? 5. Check for consistency with the project's existing patterns 6. Categorize findings by severity: critical (must fix), suggestion (should fix), nit (optional) 7. For each finding, explain WHY it's an issue and suggest a specific fix 8. Summarize: overall assessment, critical issues count, suggestions count
- Focus on bugs and security first, style and naming second
- Every criticism must include a suggested fix (not just "this is wrong")
- Do not nitpick formatting if the project has a formatter (Prettier, ESLint)
- Acknowledge what's done well, not just what's wrong
- Be specific: "Line 42: this null check misses the empty string case" not "check your inputs"
- Best with: Claude Code CLI (can read git diff and full file context)
- Also works: Cursor, Windsurf, any AI tool (paste the diff)
- Expects: A git repository with staged or committed changes to review
- Summary: one-paragraph overall assessment
- Findings list: severity, file:line, description, suggested fix
- Verdict: approve, request changes, or needs discussion