pr-fix-protocol

Applies reviewer findings to pull requests as verified fixes and resolves review threads.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-fix-protocol-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-fix-protocol
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/packages/claude-dev-env/.agents/skills-archived/pr-fix-protocol
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill pr-fix-protocol-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewer findings on a pull request often stall because fixes get pushed without thread replies, threads get resolved without fixes, or outdated threads are skipped, leaving convergence gates blocked. This protocol enforces a complete unit of work per finding: fix pushed, reply posted, thread resolved. ## Core Features & Use Cases - Verified fix sequence: Follows a shared 13-step protocol covering pre-fix SHA capture, failing-test-first where behavior exists, narrow fixes, py_compile checks, explicit-path staging, single commits, and fast-forward pushes. - Atomic reply-and-resolve: Posts a reply via GitHub MCP (or a fallback script) and resolves each thread immediately, so no thread is left half-addressed. - Unresolved-thread sweep: A hard gate that re-verifies every unresolved thread against current HEAD, including outdated ones, before a caller can advance a phase or record a clean SHA. - Use Case: A PR-loop orchestrator like pr-converge receives reviewer findings, invokes this protocol with the PR URL and worktree path, and drives the unresolved thread count to zero before marking the PR ready. ## Quick Start Invoke the pr-fix-protocol skill with the caller identity, PR URL, worktree path, and this round's reviewer findings to apply verified fixes and resolve all review threads.

Frequently Asked Questions about pr-fix-protocol

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

FAQPage Schema
How do I apply reviewer findings to a GitHub pull request automatically?▼

Invoke this protocol with the PR URL, worktree path, and findings payload. It reads each file:line, captures the pre-fix SHA, writes a failing test where behavior exists, applies a narrow fix, commits, pushes, then replies and resolves each thread atomically.

How do I resolve all unresolved review threads on a pull request?▼

Fetch review comments via the GitHub MCP pull_request_read method and filter threads where is_resolved is false. Verify each concern against current HEAD, fix and reply where it holds, or reply with an explanation where it does not, then resolve each thread.

Should outdated review threads be skipped during a PR sweep?▼

No. GitHub marks a thread outdated when its anchor line changes, but the concern can still apply to current HEAD. Verify every outdated thread against current HEAD like any other unresolved thread before resolving it.

When should this protocol not be used?▼

It is designed for PR-loop orchestrators responding to reviewer findings, not ad-hoc fix requests outside a PR loop. It also stops when the Agent tool is unavailable for spawning a clean-coder executor in single-PR loops.

What happens if no commit lands after applying a fix?▼

An unchanged HEAD after the commit step means no commit landed. The protocol exits with a stuck status rather than reporting the findings as fixed, preventing false convergence signals.