release

Automate semantic versioning and changelog updates from Conventional Commits.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill release-fppfurtado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fppfurtado/pragmatic-dev-toolkit/tree/main/skills/release
Command: npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill release-fppfurtado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the release process by automatically determining the next version from Conventional Commits, updating declared version files, and recording a changelog entry, all within a local, non-pushed workflow to reduce human error and ensure traceable releases.

Core Features & Use Cases

  • Semantic versioning: Infer major/minor/patch bumps from commit history and predefine explicit version overrides.
  • Version file synchronization: Update files specified in version_files to reflect the new version.
  • Changelog automation: Create a changelog entry documenting the release changes locally.
  • Local tagging: Produce an annotated git tag for the release without pushing.
  • Safety and gating: Enforces pre-conditions (clean working tree, correct branch) and avoids automatic pushes to protect release integrity.

Quick Start

Run the release skill to infer the next version from the Conventional Commits log and update version_files, write a changelog entry, commit changes locally and create an annotated tag.

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 from conventional commits?

Automating semantic versioning from conventional commits involves parsing your latest git tag to infer major, minor, or patch bumps, then updating version files and generating a changelog entry locally.

How do I generate a changelog and update version files for a local release?

To generate a changelog and update version files for a local release, the automation parses commit history, applies a version bump, modifies declared version files, and records changes without automatically pushing to remote.

Does the release workflow require a clean working tree and default branch?

Yes, the release workflow requires a clean working tree and the default branch as safety preconditions to ensure release integrity and prevent uncommitted changes from affecting the automated version bump.

Can I force a specific version bump instead of inferring it from commit history?

Yes, you can force a specific version bump instead of inferring it from commit history by providing an explicit version override, bypassing the conventional commits parsing logic for your release.

Does creating an annotated git tag automatically push commits to the remote repository?

No, creating an annotated git tag does not automatically push commits to the remote repository; the workflow keeps changes local and requires explicit user action to push, protecting release integrity.

What happens if my repository working tree is not clean during the version bump?

If your repository working tree is not clean during the version bump, the safety gating preconditions will fail, halting the local release automation to prevent uncommitted changes from being tagged.