release

Automate software releases with versioning, changelog generation, and GitHub releases.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mia-cx/.agents --skill release-mia-cx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mia-cx/.agents/tree/main/skills/release
Command: npx skills add https://github.com/mia-cx/.agents --skill release-mia-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release workflow for software projects, including version bumping, changelog generation, and GitHub releases, reducing manual steps and human error.

Core Features & Use Cases

  • Changesets Release flow when changesets are configured
  • Manual release flow when changesets aren't set up
  • Generates CHANGELOG.md entries
  • Tags releases and creates GitHub releases
  • Provides prompts for user confirmation during edits

Quick Start

Trigger a release workflow for the current repository and publish a GitHub release after reviewing changes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub releases and changelog generation?

This Skill automates GitHub releases and changelog generation by detecting pending changesets, computing version bumps, updating CHANGELOG.md, committing tags, and publishing the release directly to GitHub.

Do I need changesets configured to automate versioning and releases?

No, you do not need changesets configured. The workflow supports a changesets-based flow when configured, and automatically falls back to a manual release path to compute the next version if changesets are not set up.

Can I automate releases for multiple packages in a monorepo?

Yes, you can automate releases for multiple packages in a monorepo. The workflow is designed to handle both mono- and multi-package repositories, guiding the versioning and changelog process across all included packages.

How does changeset versioning update CHANGELOG.md and create git tags?

Changeset versioning updates CHANGELOG.md and creates git tags by running the changeset version command or computing the next release manually, writing changelog entries, committing the version bump, and applying the corresponding git tag.

When should I use a manual release flow instead of changesets?

You should use a manual release flow instead of changesets when your project does not have changesets configured. The workflow detects this setup and computes the next release version directly without relying on pending changeset files.