pr-review-fix

Collects unresolved GitHub PR review threads and automates fixes, replies, and resolution.

1|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/void2610/dotfiles --skill pr-review-fix-void2610
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-fix
Source: https://github.com/void2610/dotfiles/tree/main/.claude/skills/pr-review-fix
Command: npx skills add https://github.com/void2610/dotfiles --skill pr-review-fix-void2610

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve? Addressing GitHub Pull Request review comments one by one is tedious and error-prone: you must find every unresolved thread, decide what to fix, commit changes, reply to reviewers, and resolve threads. This Skill automates that entire loop in a structured 7-phase workflow so no review comment is missed. ## Core Features & Use Cases - Unresolved Thread Collection: Uses the GitHub GraphQL API via gh CLI to fetch only unresolved (isResolved=false) review threads, with pagination support for large PRs and correct handling of fork-based PRs. - Classification & Planning: Classifies each comment by priority (required / recommended / question) and category (architecture, performance, tests, etc.), then builds a sorted fix plan persisted to a mapping JSON file so work can resume after context loss. - Safe Reply & Resolve Automation: A guarded script replies only to entries with verified commit SHAs and resolves threads, with dry-run support and skip logic that prevents accidental or duplicate replies. - Use Case: A reviewer leaves 15 comments on your PR. Run this Skill to gather all unresolved threads, get a prioritized fix plan, implement and push the fixes, then automatically reply with commit SHAs and resolve each thread. ## Quick Start Ask the AI to address all unresolved review comments on the current branch's pull request using the pr-review-fix skill.

Frequently Asked Questions about pr-review-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I address all unresolved PR review comments at once?▼

Use this Skill to fetch all unresolved review threads via the GitHub GraphQL API, classify them by priority, implement fixes as commits, then automatically reply with commit SHAs and resolve each thread. It runs as a 7-phase workflow driven by the gh CLI.

How do I find unresolved review threads on a GitHub pull request?▼

The fetch_unresolved_threads.sh script queries the GitHub GraphQL reviewThreads endpoint and filters by isResolved=false, outputting NDJSON. The REST pulls comments API lacks the isResolved field, so GraphQL is required for this filtering.

Does it work with pull requests from forked repositories?▼

Yes. The scripts extract the base repository owner and name from the PR URL rather than the local git remote, so review threads on the upstream repository are correctly referenced even for fork-based PRs.

What tools are required to run the PR review fix scripts?▼

You need an authenticated gh CLI (v2.4.0+ recommended) and git. The fetch script uses gh api's built-in gojq so jq is not needed for phases 1-6, but the process_replies.sh script in the final phase requires jq for mapping file parsing.

Why does resolving a review thread fail with a 403 error?▼

A 403 on the resolveReviewThread mutation means insufficient permissions. Confirm gh is authenticated with the correct account, that the account has triage or higher access to the repository, and that the token includes the repo scope.

Can it accidentally reply to the wrong review comment?▼

No. The process_replies.sh script only sends replies for entries marked reply_eligible with a body matching the exact SHA format, and it verifies the commit_hash matches the SHA in the reply body. A dry-run mode lets you preview targets before sending.