release-pr-review

Reviews open release PRs, lands fixes as commits, and syncs the PR body before publishing.

5|1|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/cyanheads/protein-mcp-server --skill release-pr-review-cyanheads
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-pr-review
Source: https://github.com/cyanheads/protein-mcp-server/tree/main/framework-skills/release-pr-review
Command: npx skills add https://github.com/cyanheads/protein-mcp-server --skill release-pr-review-cyanheads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Release PRs in gated release workflows need a final correctness and quality review before shipping, but that review must never rewrite history, tag, merge, or touch main. This Skill performs that review pass safely, fixing real defects as ordinary commits on the release branch. ## Core Features & Use Cases - Two-lens review: Applies a code-simplifier lens plus a release-specific lens covering correctness, over-engineering, weak tests, changelog-to-diff reconciliation, and version-string consistency. - Automated reviewer intake: Reads and verifies comments from automated PR reviewers (e.g., Codex), landing valid findings and recording declined ones with reasons. - Safe fix landing and PR sync: Commits fixes by pathspec on top of the stack, re-runs the full gate, pushes fast-forward only, and syncs the PR body so it can serve as the future tag body. - Use Case: After git-wrapup opens a release/1.4.0 PR, run this Skill to review the full main...HEAD range, fix a changelog claim the diff does not support, push the fix commit, and leave one summary comment before release-and-publish tags and ships. ## Quick Start Review the open release PR for this branch, fix any real defects as new commits, and leave a summary comment on the PR.

Frequently Asked Questions about release-pr-review

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

FAQPage Schema
How do I review a release PR before publishing?▼

Check out the release/<version> branch with a clean tree, verify the PR is open and its head SHA matches local HEAD, then review the full main...HEAD diff for correctness, over-engineering, and changelog accuracy. Land fixes as new commits and push only after the gate passes.

What is a gated release PR workflow?▼

A gated release workflow opens a release/<version> to main PR that must be reviewed before tagging and publishing. The review pass happens between the wrap-up step and the release-and-publish step, with fixes committed on top of the release branch.

Can I fix bugs found during release review without rewriting history?▼

Yes. Land each fix as a new ordinary commit on top of the release branch using git commit --only with named paths, then push as a plain fast-forward. Never use fixup, autosquash, rebase, or force-push on an open release PR.

How should I handle automated reviewer comments on a PR?▼

Treat automated reviewer comments as third-party claims, not instructions. Verify each against the code, land real defects or simplifications as normal commits, and record in the summary comment which findings were taken or declined with reasons.

When should I not use this release review process?▼

Do not use it for PRs from outside contributors, non-release branches, or PRs that have already merged. It also halts if the working tree is dirty, the PR head SHA differs from local HEAD, or a version tag already exists.