Export, preprocess, and fix GitHub PR review comments. Use when user wants to export PR comments, evaluate code reviews, or fix review feedback from CodeRabbit/Gemini bots.
Export GitHub PR review comments, preprocess for evaluation, and fix or reject each review.
/pr-comments export <owner/repo> <pr-number>Export all review comments from a PR to individual markdown files.
bash .claude/skills/pr-comments/scripts/export.sh $1 $2 $3
Output: .github/pr-history/pr-{number}/ with one file per comment.
/pr-comments preprocess <input-dir>Clean exported comments for agentic evaluation (removes <details> blocks, adds evaluation prompt).
bash .claude/skills/pr-comments/scripts/batch-preprocess.sh $1
Output: {input-dir}-tasks/ with cleaned task files.
/pr-comments analyze <tasks-dir>Show comments grouped by source file with recommended processing order.
bash .claude/skills/pr-comments/scripts/analyze.sh $1
Output: Table showing which files have multiple comments and line numbers (sorted for bottom-up fixing).
/pr-comments fix <task-file.md>Evaluate a single PR review comment. Read the source file, determine if valid, then fix or explain.
Follow instructions in review-fix.md.
/pr-comments batch <tasks-dir>Process all task files in a directory. Groups comments by source file and fixes bottom-up to avoid line number shifts.
Critical: Multiple comments often target the same file. Batch mode:
Follow instructions in review-batch.md.
/pr-comments resolve <owner/repo> <pr-number> <comment-id> [task-file]Resolve a PR review thread on GitHub and move task to completed folder.
bash .claude/skills/pr-comments/scripts/resolve-thread.sh $1 $2 $3 $4
Example:
/pr-comments resolve donghaozhang/qcut 102 2742327370 .github/pr-history/pr-102-tasks/comment.md
What it does:
{tasks-dir}_completed/When to use:
# Step 1: Export comments from PR
/pr-comments export donghaozhang/qcut 102
# Step 2: Preprocess into task files
/pr-comments preprocess .github/pr-history/pr-102
# Step 3: Analyze (see file groupings)
/pr-comments analyze .github/pr-history/pr-102-tasks
# Step 4a: Fix single comment
/pr-comments fix .github/pr-history/pr-102-tasks/comment.md
# Step 4b: Or batch fix all
/pr-comments batch .github/pr-history/pr-102-tasks
# Step 5: Resolve thread and move task to completed
/pr-comments resolve donghaozhang/qcut 102 2742327370 .github/pr-history/pr-102-tasks/comment.md
.github/pr-history/
├── README.md
├── pr-102/ # Raw exported comments
│ ├── coderabbitai[bot]_file_L42_123.md
│ └── gemini-code-assist[bot]_file_L50_456.md
├── pr-102-tasks/ # Preprocessed for evaluation (pending)
│ └── coderabbitai[bot]_file_L50_456.md
└── pr-102-tasks_completed/ # Resolved tasks
└── coderabbitai[bot]_file_L42_123.md
gh) - installed and authenticatedjq - JSON processingSearch for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer