resolve

Implements, verifies, and resolves open review comments on a pull request.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill resolve-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve
Source: https://github.com/kieranpotts/skills/tree/main/skills/resolve
Command: npx skills add https://github.com/kieranpotts/skills --skill resolve-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a code review, someone must manually work through every open comment thread on a pull request — implementing each fix, verifying it, replying, and marking threads resolved. This Skill automates that entire resolution pass so no open comment is silently skipped or falsely closed. ## Core Features & Use Cases - Comment-by-comment resolution: Collects every unresolved review thread from the review host (e.g., GitHub via gh), implements the smallest faithful fix for each, and orders fixes by dependency so structural changes land first. - Verified resolutions: Every resolved thread is backed by a test that fails before the fix and passes after, plus a reply naming what changed and where, so reviewers can confirm without re-reading the diff. - Honest reporting of blockers: Comments that cannot be actioned — contradictions, missing components, out-of-scope redesigns — are left open and reported with specific reasons instead of being falsely resolved. - Use Case: After a curated review leaves three open threads on PR #482, invoke the Skill to implement all three fixes, verify each with tests, reply and resolve the threads, commit the work separately, and push the branch for re-review. ## Quick Start Ask the agent to action the open review comments on the current pull request and resolve each thread after verifying the fix.

Frequently Asked Questions about resolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve all open review comments on a GitHub pull request?▼

Run this Skill against the pull request: it queries unresolved review threads via the gh CLI, implements each requested fix, verifies it with a test, replies with what changed, and marks each thread resolved using GitHub's resolveReviewThread mutation.

How to address code review feedback automatically?▼

Invoke the Skill after a review has been curated. It treats every still-open comment as a commitment, orders fixes by dependency, applies the smallest faithful change for each, and commits the resolutions separately from the commits under review.

Does this work with review hosts other than GitHub?▼

The Skill discovers the review host from the environment rather than assuming one, but it requires a host that exposes resolvable threads. Where no resolve API exists, it records resolutions in replies and commit messages for a human to close manually.

What happens when a review comment cannot be implemented?▼

Unactionable comments are left open and reported with a specific reason, such as a missing component, contradictory comments, or an out-of-scope redesign. The Skill never marks a thread resolved just to close it out.

When should I not run an automated review resolution pass?▼

Do not run it against an uncurated review, since every open comment gets implemented in full. Curate the review first so only comments the author actually wants actioned remain open.

Does resolving review comments merge or close the pull request?▼

No. The Skill stops after pushing the resolution commits, leaving the pull request open and in review. Merging, closing, or otherwise advancing the pull request is explicitly out of scope.