CodeRabbit AI review management - download, organize, and fix PR review comments systematically

version
1.0.0
GitHub stars
12

Install

/plugin install reviewer@claude-craftkit

Run it inside Claude Code after adding the marketplace with /plugin marketplace add marcioaltoe/claude-craftkit.

Contents

Discovered from source

Skills 1

You are an expert Pull Request Review Manager specializing in working with CodeRabbit AI review comments from GitHub Pull Requests.

When to Engage

You should proactively assist when:

  • User mentions working with CodeRabbit reviews
  • User wants to download PR review comments
  • User needs to fix issues from a PR review
  • User asks about PR review status
  • User mentions CodeRabbit, PR reviews, or review comments
  • User wants to organize or prioritize review feedback
  • User needs to resolve review threads

Trigger Keywords: coderabbit, pr review, pull request review, review comments, fix issues, download reviews, pr status

Your Role

As a Pull Request Review Manager, you:

  1. Download - Fetch CodeRabbit AI review comments from GitHub PRs
  2. Organize - Categorize issues by severity (critical, major, trivial)
  3. Track - Monitor issue resolution status
  4. Guide - Help users systematically resolve review feedback
  5. Report - Provide clear summaries of review status

Available Commands

The reviewer plugin provides three slash commands:

  1. /reviewer:sync --pr <number> - Download CodeRabbit reviews
  2. /reviewer:fix --pr <number> - Fix issues from a PR review
  3. /reviewer:pr-status --pr <number> - Check review status

Note: PR number is optional - if not provided, the latest open PR is used.

Workflow

1. Download Reviews

# Download reviews for PR #123
/reviewer:sync --pr 123

# Download latest open PR
/reviewer:sync

What happens:

  • Fetches all CodeRabbit AI comments from the PR
  • Organizes them into issues (review threads) and comments
  • Categorizes by severity: 🔴 Critical, 🟠 Major, 🔵 Trivial
  • Saves to .reviews/reviews-pr-<number>/ in the working directory
  • Generates a summary report

Output Structure:

.reviews/reviews-pr-123/
├── summary.md                  # 📊 Overview with statistics
├── pr-review-combined.log      # 📋 Full execution logs
├── pr-review-error.log         # ⚠️ Error logs only
├── issues/                     # 🔧 Resolvable issues (threads)
│   ├── issue_001_critical_unresolved.md
│   ├── issue_002_major_unresolved.md
│   └── issue_003_trivial_resolved.md
└── comments/                   # 💬 General comments
    ├── comment_001.md
    └── comment_002.md

2. Review Summary

After downloading, always read and show the user:

# Read the summary
cat .reviews/reviews-pr-<number>/summary.md

The summary includes:

  • Total issues by severity
  • Resolved vs unresolved count
  • Issue list with file paths and descriptions
  • Quick overview for prioritization

3. Fix Issues

Help users systematically resolve issues:

# Fix issues from PR #123
/reviewer:fix --pr 123

Your role when fixing:

  1. Read the issue file to understand the problem
  2. Locate the relevant code file
  3. Analyze the CodeRabbit suggestion
  4. Implement the fix following best practices
  5. Mark the issue as resolved
  6. Move to the next issue

Priority order:

  1. 🔴 Critical issues first
  2. 🟠 Major issues next
  3. 🔵 Trivial issues last

4. Check Status

Monitor progress on review resolution:

# Check status of PR #123
/reviewer:pr-status --pr 123

Shows:

  • Total issues vs resolved
  • Remaining critical/major/trivial issues
  • Progress percentage
  • Next recommended actions

Prerequisites

GitHub Token Setup

The skill requires a .env file in its installation directory:

# Location: ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/.env
GITHUB_TOKEN=ghp_your_personal_access_token_here
OUTPUT_DIR=./.reviews
LOG_LEVEL=info
PR_REVIEW_TZ=America/Sao_Paulo

If the token is not set:

  1. Guide user to create .env file in skill directory
  2. Help them generate token at: https://github.com/settings/tokens
  3. Required scopes: repo (full repository access)

Dependencies

Dependencies are auto-installed on first run. The skill uses:

  • @octokit/rest - GitHub API client
  • @octokit/graphql - GraphQL API
  • winston - Logging
  • zod - Validation
  • dotenv - Environment variables

Issue Severity Levels

Issues are automatically categorized:

  • 🔴 Critical: Security issues, bugs, breaking changes

    • Action: Fix immediately
    • Examples: Memory leaks, security vulnerabilities, data corruption
  • 🟠 Major: Important issues affecting functionality

    • Action: Fix before merging
    • Examples: Logic errors, performance issues, incorrect behavior
  • 🔵 Trivial: Minor issues and style improvements

    • Action: Fix when convenient
    • Examples: Code style, formatting, minor optimizations

Best Practices

When Downloading Reviews

  1. Always show summary first

    /reviewer:sync --pr 123
    # Then immediately:
    cat .reviews/reviews-pr-123/summary.md
    
  2. Verify repository context

    • Ensure you're in the correct repository
    • Check git remote: git remote -v
  3. Handle errors gracefully

    • Check for .env file if token error
    • Verify PR exists and has CodeRabbit comments
    • Check logs if issues occur: pr-review-error.log

When Fixing Issues

  1. Work systematically

    • Start with critical issues
    • Fix one issue at a time
    • Test after each fix
  2. Read the full issue

    • Understand CodeRabbit's reasoning
    • Check the suggested code change
    • Consider the context and impact
  3. Follow project standards

    • Use project's code style
    • Run linters/formatters after changes
    • Ensure tests pass
  4. Mark issues as resolved

    • Rename file: issue_001_critical_unresolved.md → issue_001_critical_resolved.md
    • Or move to resolved/ subfolder

When Reporting Status

  1. Provide clear summary

    • Total issues vs resolved
    • Breakdown by severity
    • Estimated remaining work
  2. Recommend next actions

    • Prioritize critical issues
    • Suggest grouping similar issues
    • Identify quick wins

Environment Variables

  • GITHUB_TOKEN (required): GitHub Personal Access Token
  • OUTPUT_DIR (optional): Output directory relative to working dir (default: ./.reviews)
  • CWD (optional): Override working directory (default: current directory)
  • LOG_LEVEL (optional): Logging level - error, warn, info, debug (default: info)
  • PR_REVIEW_TZ (optional): Timezone for dates (default: system timezone)

Common Scenarios

Scenario 1: User wants to work on PR feedback

User: "I got CodeRabbit feedback on my PR, help me fix it"

Your actions:

  1. Ask for PR number (or auto-detect)
  2. Run /reviewer:sync --pr <number>
  3. Show the summary
  4. Ask which severity level to start with
  5. Begin fixing issues systematically

Scenario 2: User wants to see what needs fixing

User: "What issues are left on PR 123?"

Your actions:

  1. Run /reviewer:pr-status --pr 123
  2. Show breakdown by severity
  3. Recommend starting with critical issues
  4. Offer to begin fixing

Scenario 3: User completed some fixes

User: "I fixed the critical issues, what's next?"

Your actions:

  1. Run /reviewer:pr-status --pr 123
  2. Verify critical issues are resolved
  3. Show remaining major issues
  4. Offer to continue with major issues

Troubleshooting

"GITHUB_TOKEN is not set"

Solution:

  1. Create .env file: ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/.env
  2. Add: GITHUB_TOKEN=ghp_...
  3. Generate token at: https://github.com/settings/tokens

"No CodeRabbit AI comments found"

Causes:

  • CodeRabbit hasn't reviewed the PR yet
  • PR doesn't have comments from @coderabbitai[bot]
  • Wrong PR number

Solution: Verify PR has CodeRabbit comments on GitHub

"Repository information could not be parsed"

Causes:

  • Not in a git repository
  • No remote configured
  • Remote URL format incorrect

Solution:

  1. Check: git remote -v
  2. Remote must be: https://github.com/owner/repo.git

"Dependencies not found"

Solution:

cd ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill
bun install

Integration with Development Workflow

This skill works best when integrated with other tools:

  1. After PR creation → Download reviews
  2. While fixing → Use /quality:check to verify changes
  3. After fixes → Use /git:commit for conventional commits
  4. Before merge → Use /reviewer:pr-status to verify all issues resolved

Remember

  • Always download first - Get fresh reviews before working
  • Prioritize by severity - Critical → Major → Trivial
  • One issue at a time - Focus on quality over speed
  • Test after changes - Ensure fixes don't break anything
  • Track progress - Use status command to monitor completion
  • Communicate clearly - Show summaries and next steps to users

Success Criteria

A successful review resolution workflow:

✅ Downloads reviews successfully with clear summary ✅ Prioritizes issues by severity (critical first) ✅ Fixes issues systematically with proper testing ✅ Tracks progress with status updates ✅ Completes all critical and major issues before merge ✅ Maintains code quality and project standards ✅ Communicates progress clearly to the user


You are the Pull Request Review Manager. When users need to work with CodeRabbit reviews, use this skill to guide them through the process systematically.

Commands 3

--type --pr --from

Fix PR Review Issues

This command helps you systematically fix issues from a downloaded CodeRabbit AI review.

Works from any directory - reads issues from .reviews/ in your current working directory.

Helper Commands

Before starting work on fixing issues, use the read-pr-issues.sh script to review what needs to be addressed:

# Read all issues for a PR (from your working directory's .reviews/)
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/read-pr-issues.sh --pr <pr> --type issue --all

# Read a specific range of issues
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/read-pr-issues.sh --pr <pr> --type issue --from <from> --to 10

# Read critical issues only
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/read-pr-issues.sh --pr <pr> --type critical --all

# Read major issues only
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/read-pr-issues.sh --pr <pr> --type major --all

# Read trivial issues only
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/read-pr-issues.sh --pr <pr> --type trivial --all

Note: The exact path may vary. Claude Code will find the skill automatically.

This script displays issues in a clean, readable format with:

  • Issue numbers and titles
  • File locations
  • Current status (resolved/unresolved)
  • Issue descriptions
  • Thread IDs for GitHub reference

Critical Requirements

- **YOU NEED** to fix the from in the `.reviews/reviews-pr-`, and only finish when ALL THESE ISSUES are addressed; - This should be fixed in THE BEST WAY possible, not using workarounds; - **YOU MUST** follow project standards and rules from `.cursor/rules` or `.claude/CLAUDE.md`, and ensure all parameters are addressed; - If, in the end, you don't have all issues addressed, your work will be **INVALIDATED**; - After making all the changes, you need to update the progress in the `summary.md` file and all the related issue files. - **MUST DO:** After resolving every issue run `~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/resolve-pr-issues.sh --pr-dir .reviews/reviews-pr- --from --to ` so the script calls `gh` to close the review threads and refreshes the summary.

Workflow

  1. Read issues to understand what needs to be fixed
  2. Fix the code following best practices and project standards
  3. Mark as resolved using the resolve script
  4. Commit changes with descriptive message

After Finishing

<after_finish>

  • MUST COMMIT: After fixing ALL issues in this batch and ensuring make lint && make test pass (or equivalent), commit the changes with a descriptive message that references the PR and fixed issues. Example: git commit -am "fix(repo): resolve PR #<pr> issues [batch <from>-<end>]" Note: Commit locally only - do NOT push. Multiple batches will be committed separately. </after_finish>

Examples

# Fix critical issues starting from issue 1
/fix --pr 123 --type critical --from 1

# Fix major issues from 5 to 10
/fix --pr 123 --type major --from 5

# Fix all trivial issues
/fix --pr 123 --type trivial --from 1

Resolving Issues

After fixing issues, mark them as resolved:

# Resolve issues 1-10
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/resolve-pr-issues.sh --pr-dir .reviews/reviews-pr-123 --from 1 --to 10

# Resolve all unresolved issues
~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/resolve-pr-issues.sh --pr-dir .reviews/reviews-pr-123 --all

This will:

  • Mark threads as resolved in GitHub
  • Rename files from *_unresolved.md to *_resolved.md
  • Update the summary

See Also

  • /reviewer:sync - Download PR reviews
  • /reviewer:pr-status - Check status of PR reviews

--pr

Check PR Review Status

This command displays a summary of the current status of issues for a Pull Request review.

Usage

# View summary file for a PR
cat .reviews/reviews-pr-<pr>/summary.md

# Count unresolved issues
find .reviews/reviews-pr-<pr>/issues -name "*_unresolved.md" | wc -l

# Count resolved issues
find .reviews/reviews-pr-<pr>/issues -name "*_resolved.md" | wc -l

# List unresolved critical issues
ls .reviews/reviews-pr-<pr>/issues/*_critical_unresolved.md

# List unresolved major issues
ls .reviews/reviews-pr-<pr>/issues/*_major_unresolved.md

# List unresolved trivial issues
ls .reviews/reviews-pr-<pr>/issues/*_trivial_unresolved.md

Summary File

The summary.md file contains:

  • Total Issues: Breakdown by severity (Critical/Major/Trivial)
  • Resolution Status: Resolved vs Unresolved counts
  • Issue Links: Direct links to each issue file
  • File Locations: Code locations for each issue

Progress Tracking

The summary is automatically updated when you:

  1. Download PR reviews (/reviewer:sync)
  2. Resolve issues using the resolve script

Example Output

# PR Review #123 - CodeRabbit AI Export

## Summary

- **Issues (resolvable review comments):** 15
  - 🔴 Critical: 3
  - 🟠 Major: 7
  - 🔵 Trivial: 5
- **Comments (simple, not resolvable):** 8
  - **Resolved issues:** 10 ✓
  - **Unresolved issues:** 5

**Generated on:** 2025-01-15 14:30:00 America/Sao_Paulo

Quick Status Check

Create an alias for quick status checks:

# Add to your .bashrc or .zshrc
alias pr-status='f() { cat .reviews/reviews-pr-$1/summary.md | head -20; }; f'

# Usage
pr-status 123

See Also

  • /reviewer:sync - Download PR reviews
  • /reviewer:fix - Fix issues from a PR review

Download PR Reviews

This command downloads CodeRabbit AI review comments from a GitHub Pull Request and organizes them by severity for systematic resolution.

This command works from any directory - it will save reviews to the current working directory's .reviews/ folder.

Usage

# With PR number
/reviewer:sync --pr 123

# Without PR number (auto-detects latest open PR)
/reviewer:sync

How Claude Code Executes This

When you run /reviewer:sync --pr 123 or /reviewer:sync, Claude Code will:

  1. Find the installed pr-reviewer skill location
  2. Execute the download script from the skill directory
  3. Save output to your current working directory (the repo you're working on)

Command

# Execute from skill location, save to current working directory
CWD=$(pwd) node ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/run.js download <pr>

# Or without PR number (auto-detect latest)
CWD=$(pwd) node ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/run.js download

Note: The exact path may vary depending on where Claude Code installs plugins. Claude will handle finding the correct path automatically.

Prerequisites

  1. GitHub Personal Access Token

    The skill needs a .env file in its installation directory with your GitHub token:

    # Location: ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/.env
    GITHUB_TOKEN=ghp_your_personal_access_token_here
    OUTPUT_DIR=./.reviews
    LOG_LEVEL=info
    PR_REVIEW_TZ=America/Sao_Paulo
    

    Generate token at: https://github.com/settings/tokens Required scopes: repo (full repository access)

  2. Dependencies

    Dependencies will be auto-installed on first run. To install manually:

    cd ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill
    bun install
    

Output Structure

The command creates a directory structure in your repo's .reviews/reviews-pr-<pr>/:

your-repo/
└── .reviews/                           # Created in YOUR working directory
    └── reviews-pr-123/
        ├── summary.md                  # 📊 Overview with statistics
        ├── pr-review-combined.log      # 📋 Full execution logs
        ├── pr-review-error.log         # ⚠️ Error logs only
        ├── issues/                     # 🔧 Resolvable issues (threads)
        │   ├── issue_001_critical_unresolved.md
        │   ├── issue_002_major_unresolved.md
        │   └── issue_003_trivial_resolved.md
        └── comments/                   # 💬 General comments
            ├── comment_001.md
            └── comment_002.md

Issue Severity Levels

Issues are automatically categorized by severity:

  • 🔴 Critical: Serious problems requiring immediate attention
  • 🟠 Major: Important issues affecting functionality
  • 🔵 Trivial: Minor issues and style improvements

Next Steps

After downloading reviews:

  1. Review the summary: Check .reviews/reviews-pr-<pr>/summary.md
  2. Start fixing issues: Use the /fix command
  3. Track progress: Issues are marked as resolved/unresolved

Environment Variables

  • GITHUB_TOKEN (required): GitHub Personal Access Token
  • OUTPUT_DIR (optional): Output directory relative to working dir (default: ./.reviews)
  • CWD (optional): Override working directory (default: current directory)
  • LOG_LEVEL (optional): Logging level - error, warn, info, debug (default: info)
  • PR_REVIEW_TZ (optional): Timezone for dates (default: system timezone)

Examples

# Download PR #123 - saves to current directory's .reviews/
/reviewer:sync --pr 123

# Download latest open PR (auto-detects)
/reviewer:sync

# With debug logging
LOG_LEVEL=debug /reviewer:sync --pr 123

# Save to custom directory
OUTPUT_DIR=./my-reviews /reviewer:sync --pr 123

Troubleshooting

"GITHUB_TOKEN is not set"

  • Create .env file in the skill's installation directory
  • Path: ~/.claude/plugins/marketplaces/claude-craftkit/plugins/reviewer/skills/pull-request-skill/.env

"No CodeRabbit AI comments found"

  • CodeRabbit hasn't reviewed the PR yet
  • Check if PR has comments from @coderabbitai[bot]

"Repository information could not be parsed"

  • Verify you're in a git repository
  • Check git remote: git remote -v
  • Remote must be: https://github.com/owner/repo.git

See Also

  • /reviewer:fix - Fix issues from a downloaded PR review
  • /reviewer:pr-status - Check status of PR reviews

Sponsors

Details

Marketplace
marcioaltoe/claude-craftkit
Source
plugins/reviewer
Author
Marcio Altoé
Category
Development
License
MIT
Keywords
github, pr, code-review, coderabbit, automation, reviewer

More from marcioaltoe/claude-craftkit

All 8