← ClaudeAtlas

resolve-pr-commentslisted

Resolve the review comments on an existing Azure DevOps or GitHub pull request: fetch the PR's comment threads, triage each one, draft the code fixes and replies, and — after a single human confirmation — commit, push, reply, and update thread status. Use whenever someone wants to address, resolve, handle, action, or reply to PR comments or review feedback, fix the comments on a PR, or "go through the comments on PR <id>", even if they don't say "resolve-pr-comments". It respects the reviewer — it triages and drafts, and never auto-dismisses a comment — and it makes no outward change without explicit confirmation. It acts on the comments; it does not merely summarize them. Do NOT trigger for: opening or creating a PR (that is open-pr); summarizing or reviewing a PR's diff; reviewing a plan or code risk; or merging / completing a PR. Trigger phrases: "resolve PR comments", "address the review comments", "fix the comments on PR 12345", "handle the PR feedback", "/resolve-pr-comments".
softwareone-platform/issue-to-pr · ★ 1 · Code & Development · score 67
Install: claude install-skill softwareone-platform/issue-to-pr
# Resolve PR comments Work through the review comments on an existing Azure DevOps or GitHub pull request and bring each one to a disposition — a code fix, a reply, an explanation, an intentional skip, or a hand-off. Everything up to the gate is read-only or local-only: comments are fetched, triaged, and the fixes and replies are drafted, but **no outward change happens until a single human confirmation**. Acting on a reviewer's words is people-facing and hard to retract, so the bar is the same one `open-pr` holds for creating a PR: never commit, push, reply, or resolve a thread without explicit approval. This skill respects the reviewer. It triages and drafts; it does not sit in judgement of whether a human reviewer was right, and it never silently dismisses a comment. Where a comment looks like a false positive (a tool flag that does not apply), it drafts an explanation for the human to send or edit — it does not decide the reviewer was wrong on its own. This skill **acts on** the feedback — it does not merely read and summarize. It is backend-agnostic: the platform-specific mechanics (identity check, fetch + normalize threads, post reply, set thread status) live in **backend adapter reference docs** under `resources/backends/`. The skill body detects the platform, loads the matching adapter, and works only on the **normalized thread/comment model** the adapter produces — it holds **no `az`/`gh`-specific field parsing** of its own. Its filtering and all of its write path