skills.rest
fairchild
fairchildCOMMUNITY
Explore all skills by this author →
GitHub

release

Creates semantic versioned releases with generated changelogs, Git tags, and GitHub releases.

1|Updated Nov 11, 2012
Search Tags:#automation#changelog#conventional commits#github#release#semantic versioning#git worktree
One-click install
npx skills add https://github.com/fairchild/dotfiles --skill release-fairchild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fairchild/dotfiles/tree/main/agents/shared/first-party-skills/release
Command: npx skills add https://github.com/fairchild/dotfiles --skill release-fairchild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Cutting a release manually involves checking commits, deciding the version bump, writing a changelog, tagging, pushing, and creating a GitHub release. This Skill automates that entire workflow while keeping your current working directory untouched. ## Core Features & Use Cases - Automated Release Analysis: Parses conventional commits since the last tag, suggests the next semantic version, and previews a Keep a Changelog formatted changelog. - Worktree-Aware Releases: Releases origin/main from an ephemeral worktree at ~/.worktrees/<repo>/release-<tag>, so it works safely from any branch or worktree without modifying your checkout. - Flexible Options: Supports dry-run previews, version overrides, pre-releases (alpha/beta/rc), hotfix releases from the current branch, CI status gating, and skipping CHANGELOG.md updates. - Use Case: You are on a feature branch in a worktree and want to ship v1.3.0. Run the analyze script to preview the version and changelog, then execute the release script to commit the changelog, tag, push, and publish the GitHub release automatically. ## Quick Start Ask the AI to create a new release for the current repository, starting with a dry-run preview of the suggested version and changelog.

Frequently Asked Questions about release

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

FAQPage Schema
How do I create a semantic versioned release from the command line?▼

Run the analyze script to preview commits since the last tag and the suggested version, then run the release script to commit the changelog, tag, push, and create the GitHub release. Use --dry-run first to preview without making changes.

How is the next version number determined for a release?▼

The version is derived from conventional commits since the last tag: breaking changes bump major, feat commits bump minor, and fixes bump patch. Pre-1.0 projects bump minor for breaking changes. You can override with --version vX.Y.Z.

Can I create a release from a feature branch or Git worktree?▼

Yes. The release targets origin/main by default using an ephemeral worktree at ~/.worktrees/<repo>/release-<tag>, so your current branch and working directory are never touched. Use --current-branch only for hotfix branches.

How do I create an alpha or beta pre-release version?▼

Pass --prerelease alpha (or beta, rc) to the release script. It produces versions like v1.0.0-alpha.1 and automatically increments the prerelease number if the same base version was previously tagged.

What happens if a release fails partway through?▼

The troubleshooting reference covers each failure stage: push manually with git push origin main --tags if the push failed, create the GitHub release for an existing tag with gh release create, or remove stale worktrees with git worktree remove --force.

Does the release script check CI status before publishing?▼

Yes. It checks the latest CI run on the default branch via the GitHub CLI and aborts if CI is failing or still pending. You can bypass this gate with --skip-ci when you are confident the release is safe.

Related Skills

Explore More Software Engineering Skills→
alirezarezvanialirezarezvani
25.3k

changelog-generator

Generate Keep a Changelog release notes from Conventional Commits in git history.

Community
Intermediate
BlockRunAIBlockRunAI
6.6k

release

Executes the full ClawRouter release checklist from version bump through npm publish and GitHub release.

Official
Intermediate
AIAsysAIAsys
21

aiasys-git-workflow

Enforce atomic commits, security checks, and branch policies for AIASys Git operations.

Official
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced