release

Automate changelog generation, version bumps, and annotated git tags for releases.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill release-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/release
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill release-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Release skill automates the release lifecycle for skaile.dev domains and packages, handling changelog generation, semantic versioning, and git tagging to reduce manual toil and human error.

Core Features & Use Cases

  • Three modes: status (view current version and unreleased changes), bump (increment version and update CHANGELOG.md), tag (create annotated git tag).
  • Integrated workflow: reads current version from bundle.yaml (for domains) or package.json (for packages), analyzes conventional commits to produce a Keep a Changelog format changelog, and ensures a clean working tree before tagging.
  • Safety and governance: preserves existing changelog content, requires user confirmation before bump, and never pushes tags automatically.

Quick Start

Run the release skill to check status, perform a bump, or create a git tag for a release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate changelog generation from conventional commits?

Automate changelog generation by analyzing conventional commits to produce a Keep a Changelog format file, preserving existing content while appending new release notes without manual editing.

How does semantic versioning work with git tags for releases?

Semantic versioning reads the current version from bundle.yaml or package.json, increments based on commit analysis, and creates annotated git tags locally without automatically pushing to remote.

Can I use this release tool for multi-package repositories?

Yes, release lifecycle management applies to both single and multi-package repositories, reading versions from package.json for packages or bundle.yaml for domains to handle version bumps.

What is the best way to check unreleased changes before a version bump?

Use the status mode to view the current version and unreleased changes, allowing you to verify conventional commits before confirming a version bump and updating CHANGELOG.md.

Does the release process push git tags automatically?

No, the release process never pushes git tags automatically, requiring user confirmation before bumping and ensuring a clean working tree before creating local annotated tags.

How do I update CHANGELOG.md without losing previous release notes?

The bump mode automatically preserves existing changelog content while appending new entries in Keep a Changelog format, analyzing conventional commits to categorize changes correctly.