When to use it

Use publish-pr-feedback after resolving the local work and reviewing the proposed replies. This is the manual remote stage: your approval names the actions, message bodies, and threads that may be resolved.

How it works

Figure 01

Publish only the exact actions that were approved.

  1. Approve

    Name exact actions and prepare an unsealed plan.

  2. Seal

    Explicitly invoke the publisher to seal the draft.

  3. Execute

    Invoke separately with the sealed path and digest.

ResultApproved GitHub replies and thread resolutions
These are separate approval and invocation stages. The publisher verifies the PR and source actions before any remote mutation.

After the resolver reports and stops, a new message approves exact action IDs, bodies, resolve flags, and a fresh local plan path. The resolver can then prepare an unsealed draft. One explicit publisher invocation seals that draft; a separate invocation supplies its path and exact digest to execute it.

Before publishing, the skill checks the GitHub host, repository, open PR, remote head, and source for every action. It checks for serialized retries and pins the head again before the first remote change. The approved artifact, rather than an improvised summary, determines what can be sent.

An example request

Ask your agent

“Use publish-pr-feedback to seal the approved plan at the path we just reviewed. Stop after sealing and return its path and digest for the separate execution step.”

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

A reviewable publishing process that binds each remote reply or thread resolution to an exact approved action.

Install and use

The skill’s identifier is publish-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 example requests sealing only; it does not authorize sending comments. Follow the skill’s separate execution step with the actual sealed path and digest.

Do not run concurrent publishers for the same work: GitHub’s retry-marker check and comment creation are not atomic. The skill does not authorize commits, pushes, or merging.

  • Resolve PR feedback — Turn a GitHub review into justified local fixes and clear draft replies.