finish-release

Automate git-flow release completion with changelog updates and GitHub release creation.

577|48|Updated Aug 4, 2025
One-click install
npx skills add https://github.com/FradSer/dotclaude --skill finish-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-release
Source: https://github.com/FradSer/dotclaude/tree/main/gitflow/skills/finish-release
Command: npx skills add https://github.com/FradSer/dotclaude --skill finish-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing software from a git-flow model often requires multiple manual steps (branch finishing, changelog updates, tags, and GitHub releases). This skill automates the end-to-end release completion workflow to reduce errors and save time.

Core Features & Use Cases

  • Finish a release on main and develop branches using git-flow.
  • Auto-generate and attach release notes to a GitHub release.
  • Push all changes and tags to origin for reproducible releases.

Quick Start

  • Invoke the finish-release skill with an optional version argument (e.g., v1.2.3); if omitted, it derives the version from the current release branch.
  • It will run any configured tests, update CHANGELOG.md, perform git-flow finish, push branches/tags, and create a GitHub release with notes.

Frequently Asked Questions about finish-release

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

FAQPage Schema
How do I automate git-flow release finishing and GitHub release creation?

Automate git-flow release finishing by orchestrating version derivation, changelog updates, and GitHub release creation. The workflow finishes releases on main and develop branches, pushes all changes and tags, and generates release notes automatically.

How do I update CHANGELOG.md and push tags when finishing a release branch?

Update CHANGELOG.md and push tags by running the finish-release workflow. It reads the current branch or a provided version argument, updates the changelog, and pushes all branches and tags to origin for reproducible releases.

Do I need the git-flow-next CLI and gh CLI to finish releases automatically?

Yes, you need the git-flow-next CLI, Git, and the gh CLI to finish releases automatically. These dependencies are required to perform git-flow finish operations and create GitHub releases with auto-generated release notes.

What's the best way to generate release notes and attach them to a GitHub release?

The best way to generate release notes for a GitHub release is using an automated finish-release workflow. It auto-generates release notes from your version history and attaches them directly to the GitHub release during the git-flow finish process.

Why does my manual git-flow finish process fail to update the changelog and tags consistently?

Manual git-flow finish processes fail due to multiple repetitive steps like changelog updates and tagging. Automating the end-to-end release completion workflow reduces errors, saves time, and ensures consistent branch finishing and tag pushing.

Can I derive the version number automatically if I don't provide an argument?

Yes, you can derive the version number automatically. If you omit the version argument, the finish-release workflow derives the version directly from the current release branch name to complete the git-flow finish process.