What problem does it solve?
This Skill prevents release pull requests from being incomplete or misleading by automating the correct git comparisons and PR body formatting for SUB/WAVE.
Core Features & Use Cases
- Creates a release PR with a reviewer-friendly summary that groups non-merge commits by conventional-commit type and includes short SHAs for easy cross-checking.
- Avoids duplicate PRs by detecting an existing open release PR for
main (base) and develop (head) before creating a new one.
- Ensures release-please compatibility by targeting
origin/develop→origin/main, excluding merge commits from the summary, and instructing the operator to merge using merge commits (not squash).
Use case: You want to ship SUB/WAVE now and need a dependable PR description for what is queued on develop, without accidentally including commits already on main or producing a body that doesn’t match the project’s recent release PR conventions.
Quick Start
Say: “create a release PR from develop to main for SUB/WAVE”.