github-pr-review-loop

github-pr-review-loop

A Claude Code skill for running a disciplined GitHub PR review loop: triage every reviewer comment into apply / dismiss / clarify / defer, dismiss hallucinations with empirical evidence, resolve every thread after replying, verify CI is green before merging, and stop chasing rounds when Copilot starts repeating itself. Scales from one PR to many with parallel worktrees.

This skill encodes the habits from shipping clickwork 1.0.0 — 24 issues across ~25 PRs in ~20 hours of parallel waves — generalised so it applies to any repo with GitHub Copilot PR reviewer turned on.

When Claude should invoke this skill

• You've opened a PR and want the agent to drive it through Copilot review to merge, handling each finding correctly instead of thrashing on every suggestion.
• You're tackling a batch of related issues across many PRs and want to orchestrate parallel loops without cross-wave conflicts.
• You need to decide whether a Copilot comment is real or a hallucination, and you want evidence-backed dismissal rather than guessing.

What the skill teaches

• Triage by category. Every review finding is one of four things: apply (fix + cite commit SHA), dismiss (reply with empirical evidence), clarify (ask when ambiguous), or defer (valid but out of scope — file a follow-up issue and link it). Each has a template so the review thread stays navigable.
• Empirical dismissal. Copilot hallucinates. Before taking its word, grep -c, python -c, or a test run is cheap. The skill prescribes this check on every "this looks broken" claim.
• Correct re-request mechanics. The only way to re-trigger a Copilot review is the requestReviews(botIds: [...]) GraphQL mutation after you push fixes. @-mentioning the reviewer in a comment does nothing. The skill encodes the exact call.
• Stop conditions that aren't arbitrary. One clean Copilot pass (zero new findings) is the real signal, not some arbitrary "round 4 threshold". The skill lists the signals and an escape hatch.
• Small, focused PRs over megas. Copilot review quality degrades on large diffs — more low-signal findings, more rounds, worse throughput. The skill treats "can this be split?" as a live question during wave planning and "should this be Deferred?" as a live question during the loop.
• Plan the waves before opening implementation PRs. For multi-PR rollouts, roadmap → per-wave plan → implementation PRs, each layer reviewed and merged before the layer below opens. Prevents mid-wave pivots from mismatched API shapes across concurrent branches.
• Wave orchestration at scale. For multi-PR rollouts: parallelism policy, worktree-per-PR discipline, scheduled wake-ups instead of busy-waiting, overlap prep with Copilot bake time.

Related skills

Pairs well with superpowers:brainstorming (if you have the superpowers plugin installed) for the up-front design work the wave-planning layer asks for — invoke it before writing the roadmap or per-wave plan PR to lock in API shapes and A/B/C decisions while they're still cheap to change. This skill then drives the resulting PRs to merge.

Install

As a plugin (recommended)

Claude Code's plugin system uses a two-step marketplace flow: add this repo as a marketplace, then install the plugin from it.

# From within claude
/plugin marketplace add qubitrenegade/github-pr-review-loop
/plugin install github-pr-review-loop@qubitrenegade-github-pr-review-loop

# or from the cli
claude plugin marketplace add qubitrenegade/github-pr-review-loop
claude plugin install github-pr-review-loop@qubitrenegade-github-pr-review-loop

The first command registers the repo as a marketplace (the marketplace definition lives at .claude-plugin/marketplace.json). The second installs the plugin named github-pr-review-loop from it.

Or use the interactive UI: /plugin → Discover tab → search for github-pr-review-loop → install.

Manual (skills-only, no plugin infra)

If you just want the skill content and don't care about the plugin wrapper, copy the skill directory directly into your Claude config:

# Personal (applies to every project). Ensure the skills dir exists
# first — a fresh Claude Code install won't have it yet, and cp -r
# into a missing dir just creates ~/.claude/skills as a copy of the
# source rather than putting the source inside ~/.claude/skills/.
mkdir -p ~/.claude/skills
cp -r skills/github-pr-review-loop ~/.claude/skills/

# Or project-local (applies only to the current repo)
mkdir -p .claude/skills
cp -r skills/github-pr-review-loop .claude/skills/

This mode installs the skill only; the .claude-plugin/ manifest files aren't needed — skills work standalone. Restart your Claude Code session and the skill's metadata is loaded; the full prompt loads when Claude decides the task matches.

Requirements