stave-release

Name: stave-release
Availability: InStock
Author: sendbird-playground

Automate versioned release PR creation for the Stave repository.

3|1|Updated Mar 25, 2026

Search Tags:#automation #git #versioning #release #worktree #pr #conventional-changelog

Ready to run

npx skills add https://github.com/sendbird-playground/stave --skill stave-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stave-release
Source: https://github.com/sendbird-playground/stave/tree/main/skills/stave-release
Command: npx skills add https://github.com/sendbird-playground/stave --skill stave-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end release workflow for the Stave repository, ensuring version bumps, changelog updates, and PR creation are performed safely and reproducibly.

Core Features & Use Cases

Version bumping: patch or minor, governed by user input or explicit instruction.
Changelog generation and reconciliation: generate with conventional-changelog and validate against PR Changes and diffs.
Release worktree management: create dedicated temporary worktree, perform changes there, and clean up.
PR delivery and verification: open PR against main, include release notes, and provide verification commands and outcomes.

Quick Start

Initiate a release for the next version and follow the guided prompts to complete a release PR.

Frequently Asked Questions about stave-release

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

FAQPage Schema

How do I automate a git version bump and release PR creation?▼

To automate a git release PR, this Skill applies patch or minor version bumps, generates changelog updates with conventional-changelog, and opens a validated pull request against the main branch from a dedicated temporary worktree.

What do I need to set up before automating a semver release workflow?▼

Before automating a semver release workflow, you need a clean git working tree, an existing baseline semver tag, repository access, and the required CLI tools installed: git, gh, bunx, and conventional-changelog.

How does conventional-changelog work with git worktrees for release notes?▼

Conventional-changelog works with git worktrees by generating release notes in an isolated temporary worktree, keeping the main directory clean while reconciling changelog updates against PR diffs before opening the release PR.

Can I trigger a major version release using this automated PR workflow?▼

You cannot trigger a major version release using this automated PR workflow. The process currently validates and applies only patch or minor release types based on the previous semver tag.

What is the safest way to open a release PR without breaking the main branch?▼

The safest way to open a release PR is to create a dedicated temporary git worktree, perform version bumps and changelog generation there, validate against the previous semver tag, and clean up before opening the PR against main.