release

Cuts SemVer releases by moving CHANGELOG Unreleased entries into dated version sections with commits and tags.

15|22|Updated May 5, 2024
One-click install
npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill release-brayandiazc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/brayandiazc/project-starter-template-es-ai/tree/main/.claude/skills/release
Command: npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill release-brayandiazc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a release involves many error-prone manual steps: moving Unreleased changelog entries, picking the right SemVer bump, syncing manifest versions, and coordinating tags with CI. This Skill standardizes the entire release cut so nothing is forgotten and no version ships without a changelog entry. ## Core Features & Use Cases - Changelog-driven release cut: Moves ## [Unreleased] entries into a dated ## [X.Y.Z] section following Keep a Changelog, and updates comparison links. - SemVer bump proposal: Suggests major, minor, or patch based on the pending entries (breaking changes, Added/Changed, Fixed/Security) and asks for confirmation. - Manifest version sync: Updates the version in package.json, Cargo.toml, pyproject.toml, pubspec.yaml, and similar manifests, including lockfiles. - CI-aware tagging: Defers tag and GitHub release creation to the release.yml workflow on merge to main, with a manual fallback via gh release create when the workflow is inactive. - Hotfix flow: Supports patch releases cut directly from main on hotfix/* branches, including the required sync back to develop. - Use Case: Say "corta la versión 1.2.0" and the Skill verifies a clean tree, proposes the bump, rewrites the CHANGELOG, bumps the manifest, and commits on a chore/corte-v1.2.0 branch ready for PR. ## Quick Start Ask the assistant to cut a new release, for example: "Cut version 1.3.0 from the current Unreleased changelog entries."

Frequently Asked Questions about release

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

FAQPage Schema
How do I cut a new release from a Keep a Changelog file?▼

Run the release skill and it reads the Unreleased section of CHANGELOG.md, proposes a SemVer bump, moves the entries into a dated version section, and commits the change on a release branch. The tag and GitHub release are then created by CI on merge to main.

How is the SemVer version bump decided for a release?▼

The bump is proposed from the Unreleased content: breaking changes mean major, only Added or Changed entries mean minor, and only Fixed or Security entries mean patch. You confirm or correct the suggestion before anything is committed.

Should I create the git tag manually when a release workflow exists?▼

No. When release.yml is active, creating the tag manually makes the workflow treat the version as already published, so no GitHub release is created. Only tag manually with gh release create when the workflow is disabled or absent.

Can I cut a hotfix release directly from the main branch?▼

Yes. Hotfix branches born from main also publish a version, always a patch bump. After merging the hotfix to main, you must sync main back into develop so the fix and changelog section are not lost.

What happens if the Unreleased changelog section is empty?▼

The release stops. An empty Unreleased section means there is nothing to publish, and the skill tells you so instead of inventing changelog entries or cutting an empty version.