release

Generates changelogs, bumps versions, and creates git tags from conventional commits.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill release-cristoslc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/cristoslc/LLM-personal-agent-patterns/tree/main/L3-agents-core/.agents/skills/release
Command: npx skills add https://github.com/cristoslc/LLM-personal-agent-patterns --skill release-cristoslc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a release involves tedious manual steps: reviewing commits, deciding a version bump, writing a changelog, updating version strings across files, and tagging. This Skill automates that workflow by inferring your project's existing conventions from git history instead of requiring configuration. ## Core Features & Use Cases - Context Detection: Infers tag format, versioning scheme (semver, calver), and current version from existing git tags, and scans for version files like package.json, pyproject.toml, Cargo.toml, and SKILL.md frontmatter. - Changelog Generation: Parses conventional-commit prefixes (feat, fix, BREAKING CHANGE) to suggest a bump level and groups commits into a human-readable changelog prepended to CHANGELOG.md. - Version Bump and Tagging: Updates version strings surgically, commits the changes, creates an annotated git tag, and optionally pushes after confirmation. - Use Case: After merging a sprint's worth of conventional commits, invoke the skill to get a proposed release plan — version 1.5.0, grouped changelog, files to update — confirm it, and have the commit and tag created automatically. ## Quick Start Ask the AI to cut a release for this repository and propose a version bump with a changelog based on commits since the last tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I generate a changelog from conventional commits?▼

Parse commits since the last git tag by their conventional-commit prefixes, then group them under headings like New Features, Bug Fixes, and Documentation. Strip the prefix from each entry and prepend the grouped section to CHANGELOG.md with the new version and date.

How to decide between major, minor, and patch version bumps?▼

Use the highest-level signal from conventional commits: any BREAKING CHANGE or exclamation mark after the type means major, any feat commit means at least minor, and fix, docs, chore, refactor, test, or ci commits suggest patch. If commits lack conventional prefixes, ask the user to choose.

Does this release workflow work with monorepos?▼

Yes, it detects per-package tag patterns like frontend-v1.2.0 or api-v3.1.0 from tag history. When multiple version streams exist, it asks which package you are releasing rather than assuming one.

Can I create pre-release versions like alpha or beta tags?▼

Yes, pre-release suffixes such as 1.5.0-alpha.1 are appended to the version when requested. If prior pre-release tags exist, the existing naming convention is followed.

What happens if my working tree has uncommitted changes during a release?▼

The skill warns you about the dirty working tree before proceeding. You can choose to continue, excluding uncommitted changes from the release, or abort to commit them first.