git-release

Derive semantic version bumps and changelogs from merged PRs, updating CHANGELOG.md and outputting git tag/push commands.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill git-release-dvnghiem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/git-release
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill git-release-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates releases with consistent versioning, accurate changelogs, and proper tagging.

Core Features & Use Cases

  • Semantic versioning: Detects major, minor, and patch bumps from conventional commits, including BREAKING CHANGE notes.
  • Changelog automation: Generates human-friendly release notes and prepends them under Unreleased in CHANGELOG.md.
  • Release commands: Outputs exact git tag and push commands to publish the release.

Quick Start

Generate a release proposal from the latest merged commits, draft the changelog, and provide the exact tag and push commands.

Frequently Asked Questions about git-release

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

FAQPage Schema
How do I automate semantic versioning and changelog generation from merged PRs?

Automate semantic versioning by deriving version bumps and changelogs from merged PRs. The tool detects major, minor, and patch changes from conventional commits, updates CHANGELOG.md, and outputs exact git tag and push commands.

How does conventional commit analysis work for detecting breaking changes?

Conventional commit analysis detects breaking changes by parsing commit messages for BREAKING CHANGE notes. It then maps these notes to major version bumps, while standard commits trigger minor or patch bumps accordingly.

What is the best way to maintain consistent git tagging across multiple repositories?

Maintain consistent git tagging by automating release management across multiple repositories. The tool derives semantic versions from commit history, ensuring uniform versioning, accurate changelogs, and proper tagging.

Can I generate human-friendly release notes automatically from commit history?

Generate human-friendly release notes automatically by prepending them under the Unreleased section in CHANGELOG.md. The tool transforms conventional commits into readable summaries for publish-ready documentation.

Do I need a specific workflow to output exact git tag and push commands?

You need a workflow based on merged PRs using conventional commits. The tool processes this commit history to calculate the semantic version bump and outputs the exact git tag and push commands required.