Skill

review

Quick inline code review for devloop plan changes or PR diffs

npx claudepluginhub zate/cc-plugins --plugin devloop

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBashAskUserQuestionTaskCreateTaskUpdateTaskList

Preview

Comprehensive code review for changes, PRs, or specific files. **You do the work directly.**

SKILL.md

Similar Skills

code-review-analysis

180

Performs code reviews covering quality, security, performance, testing, maintainability, and best practices. Use for pull requests, vulnerability checks, and improvement suggestions.

8 files

aj-geddes-useful-ai-prompts-4

code-review

Automates code reviews on git diffs, staged changes, PRs, files, or branches against CLAUDE.md conventions and prioritized best practices (security first).

10 files

claude-skills

WTF Was I Thinking — Morning-After Diff Review

Reviews recent git diffs and commits with brutal honesty before PRs, spotting 2am logic flaws, copy-paste artifacts, debug leftovers, hacks, and poor naming.

4 tools

wtf

Stats

Parent Repo Stars6

Parent Repo Forks1

Last CommitMar 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Review - Code Review

Comprehensive code review for changes, PRs, or specific files. You do the work directly.

Step 1: Identify Scope

AskUserQuestion:
  questions:
    - question: "What would you like to review?"
      header: "Scope"
      multiSelect: false
      options:
        - label: "Uncommitted changes"
          description: "Review git diff"
        - label: "Staged changes"
          description: "Review git diff --cached"
        - label: "Recent commits"
          description: "Review last few commits"
        - label: "Specific files"
          description: "I'll specify paths"

Step 2: Gather Code

git diff                    # Uncommitted
git diff --cached           # Staged
git log -p -n 3            # Recent commits
gh pr diff [number]        # PR

Step 3: Review

Check these areas directly:

Correctness

Logic errors, edge cases, error handling

Security

Input validation, no hardcoded secrets, injection risks

Quality

Clear naming, no duplication, appropriate comments

Performance

No N+1 queries, proper resource handling

Step 4: Report

Present findings by severity:

## Code Review

### Critical (Must Fix)
- [Issue]: [Location] - [Problem and fix]

### High Priority
- [Issue]: [Location] - [Problem and fix]

### Suggestions
- [Minor improvements]

### Positive
- [Good patterns observed]

Step 5: Next Steps

AskUserQuestion:
  questions:
    - question: "Review complete. How proceed?"
      header: "Action"
      multiSelect: false
      options:
        - label: "Fix critical"
          description: "Address blockers only"
        - label: "Fix all"
          description: "Apply all suggested fixes"
        - label: "Accept as-is"
          description: "Proceed without changes"

If fixing, make the changes directly using Edit tool.