kata-release-prepare

Analyze Conventional Commits to propose a SemVer version and changelog draft.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-release-prepare
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-release-prepare
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-release-prepare
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-release-prepare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents release mistakes by analyzing commit history, proposing the correct SemVer bump, generating a changelog draft, and verifying trunk CI status before any publication happens.

Core Features & Use Cases

  • Conventional Commits analysis for SemVer bump: Detects major/minor/patch signals (including breaking changes and optional type override) and computes the next version; if the result is "none," it exits with a clear message instead of guessing.
  • Changelog draft generation with issue closure extraction: Groups classified commits into an ordered changelog structure and extracts referenced closed/fixed issue numbers from commit bodies.
  • Trunk state and CI safety gate: Checks CI on the exact target commit SHA and lists open PRs as informative (non-blocking), ensuring a broken trunk blocks the proposal by default.
  • Human-in-the-loop release proposal: Presents a structured approval request with versions, bump reasoning, commit counts, draft path, trunk diagnosis, and any untyped commit noise.

Quick Start

Run the kata release preparation on your repository after merging to the trunk so it can propose the next version, draft the changelog, and confirm trunk CI health for human approval.

Frequently Asked Questions about kata-release-prepare

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

FAQPage Schema
How do I automate SemVer version bumps and changelog generation from conventional commits?▼

You can automate SemVer version bumps by analyzing conventional commits and breaking-change signals since the latest tag to compute the next version and generate a structured changelog draft for release approval.

How does SemVer bump level classification work for release preparation?▼

SemVer bump level classification works by detecting major, minor, or patch signals from conventional commits, including breaking changes and optional type overrides, to compute the next version accurately.

Can I block a release publication when required CI workflows fail on the trunk?▼

Yes, you can block publication by verifying trunk CI status on the exact target commit SHA, ensuring a broken trunk blocks the release proposal by default before any publishing occurs.

What is the best way to extract closed issue numbers for a changelog draft from commit history?▼

The best way to extract closed issue numbers is by grouping classified conventional commits into an ordered changelog structure, automatically extracting referenced closed or fixed issue numbers from commit bodies.

What happens when conventional commits analysis results in a none bump level for SemVer?▼

When conventional commits analysis results in a none bump level, the process exits with a clear message instead of guessing, preventing unnecessary version increments and avoiding release mistakes.

Do I need GitHub Actions to verify trunk CI status before proposing a release version?▼

You need a CI verification process to check CI status on the target commit SHA, ensuring trunk CI health is confirmed and listed open PRs are evaluated before presenting a human-in-the-loop release proposal.