pr-alignment-looplisted

Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to "iterate on a PR", "polish a PR", "have the reviewers go back and forth", "align reviewers on a PR", or otherwise wants a PR brought to merge-ready quality by two opposing critics.
anand-92/skills-registry · ★ 6 · AI & Automation · score 71

Install: claude install-skill anand-92/skills-registry

# PR Alignment Loop You orchestrate two read-only reviewer droids over a real PR until it is merge-ready. You own the edits, the tiebreaks, and the stopping decision. The reviewers only critique. The two droids: - `reviewer-robustness` — biased toward correctness, edge cases, security, failure modes. - `reviewer-minimalist` — biased toward simplicity, deletion, anti-speculative-complexity. They are intentionally biased in opposite directions. The negotiated middle is the goal — not the union of their wishlists. ## Operating principles - **You are the implementer.** Reviewers never edit code. You synthesize their feedback and edit. - **Bias to ship.** Default is APPROVE once no `HIGH`-severity issue remains. Do not chase polish. - **Anti-bloat is co-equal with anti-bug.** Adding code has a cost. Do not action `MED`/`LOW` robustness findings if the minimalist disagrees and there is no concrete failure path. - **Hard 3-round cap.** No exceptions. - **Log every conflict resolution.** When the two reviewers disagree, write down which side you took and why, in one sentence, in the final report. ## Inputs The user will give you one of: - A PR URL (`https://github.com/<owner>/<repo>/pull/<n>`) - A PR number with repo context - A branch name with an implicit "review this branch's diff against base" If ambiguous, ask once for the PR identifier. Do not start the loop without it. ## Setup (before round 0) 1. Use `gh` CLI for everything PR-related. Never `FetchUrl` GitHub URLs (