← ClaudeAtlas

pr-resolvelisted

Resolve open review feedback on a pull request — fetch the UNRESOLVED review threads, draft a change plan from them, apply the fixes, push, then reply to each thread and mark it resolved. Use when the user says "resolve the PR", "update the PR", "address the review comments", "apply the PR feedback", "marvin resolve the PR", or "resolve PR
real-case/marvin-toolkit · ★ 0 · AI & Automation · score 68
Install: claude install-skill real-case/marvin-toolkit
# Resolve PR Turn open review feedback into code. Fetch the **unresolved** review threads on a pull request, plan the changes, apply them, push, then reply to each thread and resolve it. This is the author side of the review loop — `/marvin:pr-review` leaves the comments, this command clears them. ## Core principle **Fix what the reviewer asked, nothing more — then close the loop.** Apply the minimum change that satisfies each comment; do not refactor opportunistically. A thread is only resolved once it is actually addressed (a fix, an answer, or an explicit "won't do" with reasoning). If a comment conflicts with the spec, flag it instead of silently deviating. A comment can also be simply wrong about the code; refute it with the file and line rather than changing code that already does what it asks. ## Interactive vs. autonomous path This skill is the **interactive** path — the user invokes `/marvin:pr-resolve`, stays in the main conversation, and approves the plan and each decision inline. For the **autonomous** path — a one-shot dispatch that runs the whole cycle to completion and surfaces blockers in a final report — delegate to the `marvin-tm-review-fixer` agent via Task-tool. Both implement the same contract. ## Input `$ARGUMENTS` — optional PR number (e.g., `42`). If omitted, detect from the current branch: ```bash gh pr view --json number,headRefName,baseRefName,url -q '{number,branch:.headRefName,base:.baseRefName,url}' ``` If no PR is found, stop: "No open