prepare_release

Gather changes since the last git tag, update CHANGELOG.md, and infer the next semantic version.

270|28|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/multigres/multigres-operator --skill prepare-release-multigres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare_release
Source: https://github.com/multigres/multigres-operator/tree/main/tools/skills/prepare_release
Command: npx skills add https://github.com/multigres/multigres-operator --skill prepare-release-multigres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare a release by gathering changes since the last git tag, updating CHANGELOG.md with categorized entries, inferring the next semantic version, and auditing all documentation for staleness or missing content. Triggered by requests like "prepare release", "bump version", "update changelog", "release prep", "version bump", or "prepare changelog".

Core Features & Use Cases

  • Analyze changes since last tag: identify commits and diffs across the repository, categorize notable changes, and surface impact for changelog entries.
  • Update CHANGELOG.md with categorized entries and infer the next semantic version according to semantic versioning rules.
  • Audit documentation for staleness or missing content across the repository and prepare updates to align docs with code changes.
  • Apply doc updates to keep release notes and documentation in sync with the release.

Quick Start

Run the prepare_release skill to scan changes since the last tag and update the changelog and docs.

Frequently Asked Questions about prepare_release

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

FAQPage Schema
How do I automate changelog updates from git commits for a new release?

Automate changelog updates by analyzing commits and diffs since the last git tag, categorizing notable changes, and writing structured entries into CHANGELOG.md. This ensures release notes accurately reflect repository history without manual review.

How does semantic versioning inference work when preparing a release?

Semantic versioning inference evaluates categorized changes from your git history to determine version impact. It analyzes commits and diffs to automatically infer the next semantic version, bumping major, minor, or patch numbers based on the significance of the changes since the last tag.

What is the best way to audit documentation for staleness before a version bump?

Auditing documentation for staleness involves scanning all docs for missing content or misalignment with code changes during release prep. It identifies outdated sections across the repository and prepares updates to keep documentation in sync with the new release.

Can I use this release preparation process if my project has no git tags yet?

Release preparation relies on identifying the last git tag to gather changes, meaning it requires existing tags to calculate diffs and infer the next semantic version. Projects without prior tags may lack the baseline needed for comprehensive change categorization.

How do I categorize notable changes from git diffs for a changelog?

Categorizing notable changes from git diffs involves analyzing the impact of commits across the repository to group them into structured changelog entries. This process surfaces notable modifications and prepares categorized entries for CHANGELOG.md updates.