finish-hotfix

Automate Git-Flow hotfix completion with tests, changelog updates, and pushes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing hotfix work in a Git-Flow driven repository can be error-prone and manual. This Skill automates identifying the correct version, validating changes, updating the changelog, and applying the finish operation so hotfixes are merged consistently.

Core Features & Use Cases

  • Version determination: Derives the target version from the provided argument or the current hotfix branch name.
  • Pre-finish checks: Executes tests when available and halts on failures to ensure stability.
  • Changelog updates: Generates and updates CHANGELOG.md entries based on commit history and templates.
  • Release finish: Performs the Git-Flow hotfix finish sequence and pushes main, develop, and tags as part of the release.

Quick Start

Run finish-hotfix with an optional version argument, for example: finish-hotfix 3.1.5, to complete the hotfix on hotfix/3.1.5 and push updates.

Frequently Asked Questions about finish-hotfix

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

FAQPage Schema
Does Git-Flow hotfix automation work without predefined changelog templates?

No, predefined changelog templates are required to generate and update CHANGELOG.md entries during the hotfix finish. The automation relies on these templates to format commit history correctly.

How do I automate a Git-Flow hotfix finish?

You can automate a Git-Flow hotfix finish by running a command with an optional version argument. This executes tests, updates the changelog, and merges the hotfix branch into main and develop before pushing.

Can I run tests automatically before merging a hotfix branch?

Yes, automated pre-finish checks execute available tests and halt the hotfix operation on failures to ensure stability. This prevents broken code from being merged into main and develop branches.

How do I generate a changelog from commit history for a hotfix?

Changelog generation during a hotfix finish automatically updates CHANGELOG.md entries based on commit history and predefined templates. This ensures release notes are consistently documented before merging.

Do I need the git-flow tooling to finish a hotfix branch?

Yes, the hotfix finish automation relies on Git with git-flow tooling and predefined changelog templates to complete releases and tags. These dependencies are required for the workflow to execute correctly.

What branches are pushed when finishing a hotfix in Git-Flow?

Finishing a hotfix pushes main, develop, and tags to the remote repository as part of the release. This synchronizes the remote with the completed hotfix merge sequence.