pr-fix

Fix pull request review feedback and reply directly to review threads.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill pr-fix-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-fix
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/pr-fix
Command: npx skills add https://github.com/danielsuguimoto/skills --skill pr-fix-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing pull request review feedback involves juggling unresolved threads, branch alignment, validation, and thread-by-thread replies, which is error-prone when done manually. This Skill automates the full loop: it loads unresolved review comments, plans and implements fixes, validates them, and replies directly in each review thread. ## Core Features & Use Cases - Thread-Driven Fixes: Pulls unresolved review threads from the git host, categorizes each comment (critical, important, style, noise, question), and implements prioritized fixes on the correct PR branch. - Approval-Gated Execution: In review mode, requires explicit approval before committing, pushing, or replying; auto mode runs end-to-end without pausing. - Direct Thread Replies and Resolution: Replies inside review threads via the reply API (never standalone PR comments) and resolves fully addressed threads through GraphQL. - Use Case: A reviewer leaves eight comments on your PR, two of which are outdated. Run this Skill to check out the PR branch, fix the six actionable comments, run lint and tests, and post concise replies resolving each thread. ## Quick Start Fix the review feedback on pull request 142 and reply to each review thread after pushing the changes.

Frequently Asked Questions about pr-fix

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

FAQPage Schema
How do I address PR review comments automatically?▼

Provide the PR number or URL and the Skill checks out the PR branch, loads unresolved review threads, plans and implements fixes, runs lint and tests, then commits, pushes, and replies in each thread. In review mode it pauses for explicit approval before committing.

How to reply to GitHub review threads instead of PR comments?▼

Use the review thread reply API: POST to pulls/{pr}/comments/{comment_id}/replies, or the git host reply tool with pr_number, comment_id, and body. Standalone PR comments via gh pr comment are avoided except for flat comments without a line anchor.

Can it resolve review threads after fixing feedback?▼

Yes, after replying it resolves fully addressed threads using the GraphQL resolveReviewThread mutation, mapping comment databaseIds to thread node IDs. Threads that were intentionally skipped or reopened by reviewers are left unresolved.

Does it require approval before pushing changes?▼

In the default review mode, yes: it presents a fix summary and validation results and waits for an explicit Go Ahead decision before committing, pushing, or replying. Auto mode skips the gate and executes end-to-end.

What happens when review feedback is ambiguous or invalid?▼

Ambiguous, outdated, or invalid threads are moved to a not-fixing list with recorded reasons, and the reply explains why no change was made. Effectively resolved threads are verified against later commits before being skipped.