Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From gitflow
Begins a hotfix for a production issue using git-flow. This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gitflow:start-hotfix <version><version>haikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify working tree is clean per `${CLAUDE_PLUGIN_ROOT}/references/invariants.md`.
Verify working tree is clean per ${CLAUDE_PLUGIN_ROOT}/references/invariants.md.
Goal: Create hotfix branch using git-flow-next CLI.
Actions:
git flow hotfix start $ARGUMENTSchore: bump version to $ARGUMENTS
with Co-Authored-By footergit push -u origin hotfix/$ARGUMENTSnpx claudepluginhub rootial/dotclaude --plugin gitflowCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.