skills.rest
SumitRajpal
SumitRajpalCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Bump semantic versions, update changelogs, and tag Git releases.

Updated Mar 24, 2026
Search Tags:#automation#git#workflow#changelog#versioning#release#semver
One-click install
npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill release-sumitrajpal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/SumitRajpal/nextjs-claude-architecture/tree/main/.claude/skills/release
Command: npx skills add https://github.com/SumitRajpal/nextjs-claude-architecture --skill release-sumitrajpal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release workflow for software projects: bump version numbers, refresh changelogs, and publish Git tags and release commits, reducing manual errors and saving time.

Core Features & Use Cases

  • Version bumping based on semantic levels (major, minor, patch) with default to patch
  • Changelog generation and integration to CHANGELOG.md
  • Safe commit and tag workflow with pre-checks and user confirmation
  • Works on Git-based projects using a standard release flow including main or master branches

Quick Start

Run the release command with an optional bump level, e.g., /release minor, to bump the version, update the changelog, and create the git tag and release commit.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semantic versioning and changelog updates for a Git project?▼

Automate semantic versioning and changelog updates by running a release command that calculates the version bump, refreshes CHANGELOG.md, and creates Git tags. It defaults to a patch bump unless you specify major or minor.

How does automated release tagging work on main or master branches?▼

Automated release tagging works by applying pre-release checks to your main or master branch, calculating the semantic version bump, generating a changelog entry, and committing with a Git tag after user confirmation.

Can I create a hotfix or patch release without manually editing the changelog?▼

Yes, you can create a hotfix or patch release without manual edits. The workflow automatically calculates the patch version bump, generates changelog entries, and safely commits the changes to your Git repository.

Do I need to specify a version number when preparing a new release?▼

No, you do not need to specify a version number. You can provide a semantic level like minor or major, and the workflow defaults to a patch bump if no argument is supplied during the release process.

What is the safest way to bump versions and tag releases without manual errors?▼

The safest way to bump versions and tag releases is using an automated workflow that performs pre-checks, calculates semantic versions, updates the changelog, and prompts for user confirmation before committing Git tags.

Does the release workflow require user confirmation before pushing Git tags?▼

Yes, the release workflow requires user confirmation before completing the safe commit and tag process. This ensures you review the semantic version bump and changelog updates before finalizing the Git release.

Related Skills

Explore More Software Engineering Skills→
edfentonedfenton
3

shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

Community
Advanced
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
StaysrStaysr

version-release

Automate version tagging, changelog generation, and PR workflows for minor and patch releases.

Community
Advanced
NITRR-OfficialNITRR-Official
4

release-management

Automate semantic versioning, changelog generation, and GitHub release creation for CampusOS.

Official
Intermediate