publish-pr-review
Installation
SKILL.md
Publish PR Review
Publish the verdict and findings of a completed review from this conversation, or carry out its authorized closure recommendation. Use its evidence when composing the public copy; do not conduct another review or add findings.
Do not publish when
Stop on any of these, say which one, and ask for what would clear it.
- The user has not explicitly authorized the requested action. Publishing a review does not authorize closing the pull request. Neither action authorizes code changes, labels, reviewer requests, or merges.
- The head has moved past the revision that was reviewed. Checking the findings against the new commits is reviewing rather than publishing, so hand it back instead of doing it here, even when they look like they survive. Publishing against unreviewed code is worse than publishing late.
- You are publishing a review and every finding is already on the pull request. Read the existing reviews, threads, and PR comments first, including other people's and ones predating the reviewed revision. Drop the findings those threads already cover, say which you dropped, and stop only when nothing is left to add. This condition covers duplication alone; a moved head is condition 2 and outranks it.
- The exact review body, inline comments and locations, or closing comment have not been shown and confirmed. Show the copy itself as a separate step before any mutation; a summary or file path is not a substitute.
- The review depends on an unresolved decision from the maintainer. Return it to triage; do not resolve the review's direction while publishing.
Public copy
Write to the pull request author as a colleague discussing the change. Use the completed review and the PR conversation to decide what needs saying.