pr-review

Reviews GitHub pull requests with parallel agents and fixes open issues in isolated worktrees.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/ByronWilliamsCPA/plugin --skill pr-review-byronwilliamscpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/ByronWilliamsCPA/plugin/tree/main/plugins/wff-code/skills/pr-review
Command: npx skills add https://github.com/ByronWilliamsCPA/plugin --skill pr-review-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request review and remediation is fragmented across CI failures, review comments, SonarQube findings, and coverage reports, forcing developers to manually gather, triage, and fix issues scattered across many tools. ## Core Features & Use Cases - Tiered PR Review: The /pr-review workflow orchestrates Copilot, SonarQube, and 8 parallel analysis agents to produce a Critical/Important/Suggested/Informational findings report, including a premise gate that questions whether the change should exist at all. - Automated Issue Remediation: The /pr-fix workflow gathers all open PR issues (CI failures, review comments, SonarQube issues, Codecov, agent findings) and resolves them in an isolated git worktree without touching the main working tree. - Use Case: Given a PR URL like https://github.com/owner/repo/pull/123, run /pr-review to get a full tiered findings report, then run /pr-fix to automatically resolve CI failures, apply reviewer suggestions, and address SonarQube findings. ## Quick Start Ask the assistant to review the pull request at a given GitHub URL using /pr-review, then follow up with /pr-fix on the same URL to resolve the reported issues.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a GitHub pull request with multiple analysis agents?▼

Run /pr-review with the PR URL, for example /pr-review https://github.com/owner/repo/pull/123. It fetches all context via GitHub MCP tools without a local checkout and runs Copilot, SonarQube, and 8 parallel agents to produce a tiered findings report.

How do I automatically fix CI failures and review comments on a PR?▼

Run /pr-fix with the PR URL. It gathers CI failures, unresolved review comments, SonarQube findings, and coverage issues, classifies them by fixability, and applies fixes in an isolated worktree at .worktrees/fix-pr{N} so your main working tree is never touched.

Does pr-review require a local checkout of the repository?▼

No, the review workflow fetches all context through GitHub MCP tools and the gh CLI, so the working tree is never touched. Only /pr-fix creates a local git worktree, and only when code changes are actually needed.

What happens when a PR has merge conflicts during automated fixing?▼

The /pr-fix workflow detects CONFLICTING or BEHIND merge states and stops before applying fixes, since GitHub Actions does not reliably re-trigger checks on conflicting PRs. It asks you to choose a merge, rebase, or manual resolution first.

How are SonarQube findings handled in PR review?▼

SonarQube issues and security hotspots are treated as authoritative and bypass AI confidence scoring, so they are always included in the report. Issues and hotspots are fetched through separate API calls because SonarCloud never returns both from one endpoint.

What are the limitations of automated PR fixing?▼

Secrets findings from tools like GitGuardian are never auto-fixed, only surfaced as alerts. Human-only items such as design debates and security policy decisions are listed but not resolved, and conflicted PRs require explicit user direction before any fix work begins.