subwave-release-pr

Create a develop-to-main release pull request with a conventional-commit grouped summary.

1.2k|104|Updated May 11, 2026
One-click install
npx skills add https://github.com/perminder-klair/subwave --skill subwave-release-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subwave-release-pr
Source: https://github.com/perminder-klair/subwave/tree/main/.claude/skills/subwave-release-pr
Command: npx skills add https://github.com/perminder-klair/subwave --skill subwave-release-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

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/developorigin/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”.

Frequently Asked Questions about subwave-release-pr

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

FAQPage Schema
How do I automate a release pull request from develop to main?

To automate a release pull request from develop to main, this Skill fetches origin remotes, generates a conventional-commit grouped summary with short SHAs, and opens the PR via GitHub CLI. It targets origin/develop to origin/main to ensure compatibility with release-please promotion.

What is a conventional-commit grouped summary for a release PR?

A conventional-commit grouped summary organizes non-merge commits by their commit type, such as feat or fix, and includes short SHAs. This format provides a reviewer-friendly PR body that flags breaking changes and matches standard release PR conventions.

How do I prevent duplicate release PRs when automating develop to main?

To prevent duplicate release PRs, the automation checks for an existing open PR with main as the base and develop as the head before creating a new one. This ensures only one active release PR exists at any given time.

Does release-please work with a manually created develop to main PR?

Yes, release-please works with this PR setup because the Skill targets origin/develop to origin/main, excludes merge commits from the summary, and instructs the operator to merge using merge commits rather than squash commits.

Why does my release PR body include commits that are already on main?

A release PR body may include commits already on main if the git comparison is not correctly scoped. This Skill prevents incomplete or misleading descriptions by automating the correct git comparisons between origin/develop and origin/main.