pr-review-fix

Resolves GitHub PR review comments through a multi-agent triage, plan, audit, implement, and QA pipeline.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-review-fix-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-fix
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/pr-review-fix
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill pr-review-fix-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing a large batch of PR review comments manually is error-prone: fixes get missed, sibling code paths with the same vulnerability go unpatched, and tests pass vacuously without proving anything. This Skill runs a structured 11-phase pipeline that takes a PR's review comments from triage to fully-resolved, with dual audits at both the planning and implementation stages. ## Core Features & Use Cases - Full Comment Triage: Pulls issue comments, inline review comments, and review summaries via the GitHub CLI, categorizing them into blockers, issues, suggestions, and nits, plus linked Jira ticket context. - Dual-Audit Planning and Implementation: A planner drafts fixes while two independent auditors check the plan for security/correctness and completeness/edge-cases; the implementation then receives the same dual-audit treatment before anything is pushed. - QA, Playwright, and Post-Mortem: Verifies every fix against Jira acceptance criteria, runs relevant Playwright e2e specs, and posts a post-mortem comment documenting each fix as Problem / Solution / Why it was missed. - Use Case: A reviewer leaves 6 blocking comments on a Django backend PR. Invoke the pipeline with the repo and PR number, and it triages the comments, plans fixes, audits the plan twice, implements in a git worktree, audits the implementation twice, runs tests and Playwright, pushes, and posts a post-mortem. ## Quick Start Ask the agent to fix the review comments on PR 1246 of the backend repository using the pr-review-fix pipeline.

Frequently Asked Questions about pr-review-fix

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

FAQPage Schema
How do I fix all PR review comments automatically?

Invoke the pipeline with a repository shorthand and PR number, or a full GitHub PR URL. It triages every comment into blockers, issues, suggestions, and nits, then plans, dual-audits, implements, and verifies fixes before pushing.

How does the pipeline prevent incomplete security fixes?

Two independent plan auditors check security/correctness and completeness/edge-cases before implementation, and two implementation auditors verify the actual code changes. Checklists include patterns like scoping UUID lookups to the requesting user and applying fixes to all sibling views.

Does it work with both backend and frontend repositories?

Yes. It accepts repo aliases like be/backend for the Django backend and fe/frontend for the frontend, or a full GitHub URL. Backend fixes run Django test suites; frontend fixes run type checks, linting, and Playwright specs.

What happens if the implementation audits find problems?

A dedicated fix phase triages all audit findings rated incomplete or wrong, applies corrections in the git worktree, re-runs tests after each fix, and commits the changes before pushing the branch.

What limitations does the PR fix pipeline have?

It requires the GitHub CLI to be installed and authenticated, and QA depends on a linked Jira ticket or PR test plan for acceptance criteria. Features without existing Playwright coverage are flagged as gaps rather than automatically tested end-to-end.