final-release-review
Final Release Review
Purpose
Audit BASE_TAG...TARGET in one of two modes:
- Pre-release planning: use when the user asks to plan the next release or when the target, normally
origin/main, does not yet declare a release candidate. The user may still supply a tentativepatchorminorintent. Recommend the compatible type; do not treat unchanged package metadata as a blocker. - Final candidate: use when the user asks for a final candidate decision, the target is a release branch, or target package metadata has already been bumped beyond BASE for the next release. Compare the candidate intent with the minimum release type required by the diff.
In both modes, find concrete regressions and release risks, independently determine version compatibility, review the latest open documentation PRs before claiming coverage is missing, and produce an actionable release handoff. Keep documentation readiness separate from the release gate. The release call is a controlling checker result: callers must stop on BLOCKED and may continue only on GREEN LIGHT TO SHIP. Producing the report text is not itself a passing result.
Ordinary release: review the Release Please PR
For normal releases, invoke $final-release-review with the release PR URL or number.
Release Please owns version/changelog updates, its PR branch, tags, and GitHub Releases.
Do not invoke $release-candidate-prep, bump versions, create a competing release branch,
or create tags/releases for this route. The manual skill is an explicitly requested fallback.