release

Automate software releases by analyzing commits, bumping versions, and publishing GitHub releases.

2.6k|194|Updated Sep 12, 2025

Search Tags:#automation #git #changelog #versioning #github #release

Ready to run

npx skills add https://github.com/heyitsnoah/claudesidian --skill release-heyitsnoah

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/heyitsnoah/claudesidian/tree/main/.agents/skills/release
Command: npx skills add https://github.com/heyitsnoah/claudesidian --skill release-heyitsnoah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual release processes are error-prone and time-consuming, requiring repeated steps across versioning, changelog maintenance, git commits, tagging, and publishing releases.

Core Features & Use Cases

Automatic version bump determination from commit history (major/minor/patch) or explicit input.
Update package.json version and migrate "Unreleased" changelog entries to the new version section.
Create annotated git tags and push commits and tags to GitHub; publish GitHub releases with notes.
Enforce prerequisites (on the main branch, clean working tree, existence of CHANGELOG.md and package.json) and provide safe dry-run and confirmation options.

Quick Start

Run the release workflow to automatically bump the version, update the changelog, commit, tag, and push a GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate semantic version bumps and GitHub releases from commit history?▼

You can automate semantic version bumps by analyzing commit history to determine major, minor, or patch changes, then automatically updating package.json, generating changelog entries, and publishing a GitHub release with release notes.

How do I automatically update package.json and CHANGELOG.md during a release?▼

During a release, the version in package.json is automatically bumped and "Unreleased" entries in CHANGELOG.md are migrated to the new version section, ensuring both files stay synchronized without manual edits.

Can I enforce a clean working tree and main branch before creating a git tag?▼

Yes, the release process can enforce prerequisites like requiring a clean working tree and operating on the main branch before it proceeds with git operations like committing, tagging, and pushing.

What is the best way to dry-run a version bump and changelog update before pushing?▼

You can use a safe dry-run option to preview the version bump, changelog modifications, and git operations before actually committing, tagging, or pushing changes to GitHub.

How does automatic release determination work for major, minor, and patch versions?▼

Automatic release determination works by analyzing commit history to infer whether a major, minor, or patch version bump is required, or you can explicitly pass version flags to override the automatic detection.

How do I publish a GitHub release with automatically generated release notes?▼

After bumping the version and updating the changelog, the workflow creates an annotated git tag, pushes the commit and tag to GitHub, and publishes a GitHub Release populated with the generated release notes.