When to use it

Use resolve-pr-feedback when a pull request has accumulated review threads, review bodies, and comments. It helps work through the feedback together, including repeated bot findings and comments that no longer match the code.

How it works

Figure 01

Work through the review before replying.

  1. Collect

    Fetch the GitHub review threads and comments.

  2. Verify

    Check each claim and make authorized local fixes.

  3. Draft

    Explain the fix or reasoned disagreement.

ResultLocal changes and draft replies
The resolver stops before publishing. A separate explicit workflow handles remote replies and thread resolutions.

The skill fetches the review material with pagination and assesses each item against the actual implementation. It can identify a shared mistaken assumption behind several comments instead of treating each as an unrelated demand.

For authorized fixes, it updates the working tree and drafts replies quoting the relevant feedback. Valid concerns get a concrete resolution; incorrect findings get an explanation. Items needing your judgment are summarized with enough context to decide.

An example request

Ask your agent

“Resolve the feedback on this GitHub PR. Check each finding against the code, fix the valid issues locally, and draft replies explaining the changes or disagreement.”

This illustrates a request you can adapt; it is not a transcript of a completed run.

Local changes and a review report with draft replies, ready for you to inspect before anything is published.

Install and use

The skill’s identifier is resolve-pr-feedback. It ships in the pr-feedback plugin. In Claude Code, first add the Overclock marketplace, then install the package:

/plugin install pr-feedback@overclock

For a standalone installation, keep the skill directory and its bundled resources together. The repository also includes per-skill Codex metadata. Read the full skill instructions for its exact workflow and supporting files.

What to keep in mind

The resolver does not post comments, resolve remote threads, stage, commit, push, merge, or approve the PR. Publishing is a separate skill and explicit workflow.

The integration supports GitHub, including Enterprise. Reviewer assertions remain claims to verify, even when they come from a confident automated reviewer.

  • Test discipline — Demonstrate the bug before changing the code that is supposed to fix it.
  • Publish PR feedback — Publish the exact review replies and thread resolutions you have approved.