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.