From gitflow
Creates a new feature branch using git-flow and pushes it to the remote repository. Requires a clean working tree before branching.
How this command is triggered — by the user, by Claude, or both
Slash command
/gitflow:SKILL <feature-name>haikustart-feature/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## Workflow Execution **Launch a general-purpose agent** that executes all phases in a single task. **Prompt template**: **Execute**: Launch a general-purpose agent using the prompt template above
Launch a general-purpose agent that executes all phases in a single task.
Prompt template:
Execute the start-feature workflow.
## Pre-operation Checks
Verify working tree is clean per `${CLAUDE_PLUGIN_ROOT}/references/invariants.md`.
## Phase 1: Start Feature
**Goal**: Create feature branch using git-flow-next CLI.
1. Run `git flow feature start $ARGUMENTS`
2. Push the branch to origin: `git push -u origin feature/$ARGUMENTS`
Execute: Launch a general-purpose agent using the prompt template above
npx claudepluginhub fradser/dotclaude --plugin gitflow/featureCreates a Git Flow feature branch from develop with proper naming, remote tracking, and pre-flight validation.
/flow-startStarts a new feature, bugfix, or hotfix branch following git-flow conventions. Creates the branch from the appropriate base, sets up remote tracking, and optionally links a GitHub issue.
/git-checkoutCreates a feature branch from the default branch, pulls latest changes, and updates workflow progress in a state management file.
/worktree-startCreates a Git worktree for parallel development, automatically naming branches with type prefixes (feature/, fix/, refactor/) and detecting the project domain/framework. Also checks for Claude Code file conflicts.
/SKILLReviews a pull request, then persistently monitors CI and reviewer comments, triaging each through an independent agent until CI passes and all feedback is resolved.
/SKILLExecutes written implementation plans through phase-based orchestration with per-batch sub-agent coordinators, verification, and Git commits between batches.