Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From git-flow
Starts a new feature, bugfix, or hotfix git-flow branch from clean up-to-date base, pushes with tracking, links GitHub issues if referenced, and shows branch info plus next steps.
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin git-flowHow this command is triggered — by the user, by Claude, or both
Slash command
/git-flow:flow-startThe summary Claude sees in its command listing — used to decide when to auto-load this command
Start a new feature, bugfix, or hotfix branch following git-flow conventions. ## Steps 1. Determine the flow type from the argument: - `feature/<name>` for new features (branches from `develop` or `main`). - `bugfix/<name>` for non-critical fixes (branches from `develop`). - `hotfix/<name>` for critical production fixes (branches from `main`). 2. Verify the working tree is clean: `git status --porcelain`. 3. Fetch latest from remote: `git fetch origin`. 4. Create the branch from the appropriate base: - `git checkout -b <type>/<name> origin/<base>`. 5. Set up branch tracking: `...
/featureCreates Git Flow feature branch feature/<feature-name> from develop: validates repo and name, handles uncommitted changes, pulls latest develop, sets remote tracking, pushes to origin.
/SKILLStarts a new git-flow feature branch named feature/<feature-name> after verifying clean working tree, then pushes it to origin.
/bug-fixCreates GitHub issue and feature branch for bug ($ARG), guides implementation and testing, then commits, pushes branch, and creates linked PR.
/branchExecutes git branch operations including create from issue ID, merge with validation, delete, switch, and status, enforcing rules from project git-workflow.md.
/git-checkoutCreates and checks out a new feature branch 'feat/[issue-key]' from the default branch after pulling latest changes, and updates the working branch in the state management file.
Share bugs, ideas, or general feedback.
Start a new feature, bugfix, or hotfix branch following git-flow conventions.
feature/<name> for new features (branches from develop or main).bugfix/<name> for non-critical fixes (branches from develop).hotfix/<name> for critical production fixes (branches from main).git status --porcelain.git fetch origin.git checkout -b <type>/<name> origin/<base>.git push -u origin <type>/<name>.<type>/<issue-number>-<description>.Flow started:
Type: <feature|bugfix|hotfix>
Branch: <branch-name>
Base: <base-branch>
Tracking: origin/<branch-name>
Next steps:
1. Make your changes
2. Commit with conventional messages
3. Run: /git-flow:flow-release to merge