← ClaudeAtlas

fix-pr-mantralisted

Use when addressing pull-request review comments — "fix the review comments", a reviewer or bot (CodeRabbit, ultrareview) left comments to act on, or a PR URL/number is pasted with review feedback. Triggers on /fix-pr-mantra.
atomgunlk/skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill atomgunlk/skills
# Fix PR Mantra Four-step discipline for turning PR review comments into changes. Recite the mantra verbatim, then apply the steps in order. ## Recite this — verbatim, as the first thing in your first response > **Mantra:** > > 1. **Every comment earns a verdict.** Gather all of them; none gets silently skipped. > 2. **Decide before you touch.** Fix, won't-fix, clarify, or defer — each with a reason. > 3. **Plan, then ask.** Confirm the plan before a single edit. > 4. **Close every thread you open.** Push after the fix lands, then a one-line receipt per thread — a receipt, not a writeup. Then begin work. --- ## 1. Gather every comment Collect the full set of open feedback before reasoning about any of it. The fetch/fact-check procedure lives in **`ledger-builder.md`** in this skill's directory — one source of truth; what changes with PR size is only WHO executes it. - Resolve the PR: the current branch's PR (`gh pr view`), or the number/URL the user gave. - **Branch guard.** Confirm the checkout is on the PR's head branch (`gh pr view --json headRefName` vs `git branch --show-current`) — fact-checks read this code and step 4 commits to it. On a different branch → tell the user and get an OK to switch before gathering. - **Count first** — one cheap query decides who gathers: ```sh gh api graphql -f query=' query($owner:String!,$repo:String!,$pr:Int!){ repository(owner:$owner,name:$repo){ pullRequest(number:$pr){ reviewThreads(first:100){ nodes{ isRe