skills.rest
martin-janci
martin-janciCOMMUNITY
Explore all skills by this author →
GitHub

prepare-release

Identify the latest release tag and generate a changelog preview from commits.

Updated Jan 30, 2026
Search Tags:#automation#git#changelog#release-management#conventional-commits#version-bump#prepare-release
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill prepare-release-martin-janci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-release
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/prepare-release
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill prepare-release-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps release managers and developers quickly prepare software releases by analyzing commits since the last tag, determining the appropriate version bump, and generating a changelog preview.

Core Features & Use Cases

  • Analyze commits since the last release tag to derive a semantic version bump (major/minor/patch) in line with Conventional Commits.
  • Generate a concise changelog preview showing breaking changes, features, and fixes for upcoming release tagging.
  • Output the exact release commands (tag, changelog update, and push steps) to automate the release workflow.
  • Use Case: A project with multiple features and fixes since the last tag can automatically determine the next release version and present a ready-to-publish changelog.

Quick Start

Run the prepare-release skill to identify the latest tag, list unreleased commits, and preview the release notes.

Frequently Asked Questions about prepare-release

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

FAQPage Schema
How do I determine the next semantic version bump from conventional commits?▼

To determine the next semantic version bump from conventional commits, analyze the commit history since the latest release tag to identify breaking changes, features, or fixes, which dictate a major, minor, or patch version increment respectively.

Can I generate a changelog preview automatically before tagging a new release?▼

Yes, you can generate a changelog preview automatically before tagging a new release by gathering unreleased commits and categorizing breaking changes, features, and fixes to produce concise release notes for review.

How do I prepare a release workflow for a main branch CI pipeline?▼

To prepare a release workflow for a main branch CI pipeline, validate the branch status and commit formats, calculate the version bump, and output the exact git tagging, changelog update, and push commands for automated execution.

Does this release management approach require a strict conventional commit format?▼

Yes, this release management approach requires a strict conventional commit format to accurately validate commit messages and automatically derive the correct semantic version bump and structured changelog sections.

What is the best way to automate software release preparation in local development?▼

The best way to automate software release preparation in local development is to identify the latest tag, list unreleased commits, calculate the version bump, and preview the release notes and commands before publishing.

Related Skills

Explore More Software Engineering Skills→
sigridjinethsigridjineth
20

git-master

Manage Git repository history with atomic commits and interactive rebasing.

Community
Intermediate
mgamadeusmgamadeus
3

ddd-composer-update-version

Bump composer.json versions, commit, and create git tags for Packagist releases.

Community
Intermediate
ACuberoACubero

ci-cd-pipelines

Automate Python CI/CD pipelines with GitHub Actions for testing, linting, and releases.

Community
Advanced
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate