← ClaudeAtlas

fix-prlisted

Resolve the findings on an existing pull request - review comments, CI failures, and self-review findings - driving each to a decision (fix / defer to a tracked issue / discard), re-verifying the gates, replying to each reviewer, and watching for late feedback. The counterpart to pr-review that closes the loop.
theam/claude-dev-kit · ★ 13 · AI & Automation · score 79
Install: claude install-skill theam/claude-dev-kit
# Fix PR Drive a PR's feedback to done: run a review, triage **every** item to a decision, fix what deserves fixing, file what deserves doing later, discard what deserves nothing, answer every reviewer, and re-check after pushing in case late feedback (bots, CI) arrives. The bar for correctness is high; the bar for new machinery is low — fix the defect, don't redesign around it. ## 1. Establish the PR intent (the scope ruler) Write one or two sentences: **what this PR is for, and what it deliberately does not change** — derived from the title, body, linked issue, and the diff. Every scope call below is measured against it. If the intent is genuinely ambiguous, ask the author before triaging. ## 2. Gather the findings Collect from every surface, deduplicated. Commands below are for `github` (`prHost` in `.claude/dev-kit.json`); for **bitbucket** use the REST API (`/pullrequests/{id}` comments, `/statuses`), for **gitlab** `glab mr view/checks`. 1. **CI failures**: `gh pr checks <pr>` — read the failing job logs, not just the status. 2. **Review feedback**: unresolved inline threads, review summary bodies, and PR conversation comments — bots included (`gh pr view <pr> --comments`, `gh api` for threads). Keep outdated threads: the code moved, the concern may not have. 3. **Self-review findings** handed over by the caller (the `pr-review` pass). ## 3. Build the ledger One row per **distinct claim**, merging duplicates across sources (if the review pass and a human flagged th