Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From gitflow
Finalizes git-flow feature: verifies branch, runs tests, updates CHANGELOG.md, merges to develop, pushes origin/develop.
npx claudepluginhub fradser/dotclaude --plugin gitflowHow this command is triggered — by the user, by Claude, or both
Slash command
/gitflow:SKILL feature-namehaikufinish-feature/Files this command reads when invoked
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 4 phases in a single task. **Prompt template**: **Execute**: Launch a general-purpose agent using the prompt template above
/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.
/flow-releaseCompletes Git Flow by merging feature/bugfix/hotfix branch to target (develop/main), runs checks, creates PR, optionally auto-merges/tags, cleans up branch. Outputs completion summary.
/feature-flowOrchestrates complete git workflow: analyzes staged changes or issue number, creates branches/issues/commits, runs lints/tests, creates merge requests.
/quick-pushStages all changes, bumps version in manifests if applicable, updates CHANGELOG.md, commits semantically with Claude signature, and pushes to current or new feature branch.
/finishing-a-development-branchVerifies tests pass, pushes the current development branch to remote, and creates a pull request for merging.
/git-workflowOrchestrates git workflow from code review and quality gates through commit, push, and PR creation to target branch. Supports flags: --skip-tests, --draft-pr, --no-push, --squash, --conventional, --trunk-based.
Share bugs, ideas, or general feedback.
Launch a general-purpose agent that executes all 4 phases in a single task.
Prompt template:
Execute the finish-feature workflow (4 phases).
## Pre-operation Checks
Verify working tree is clean and current branch matches `feature/*` per `${CLAUDE_PLUGIN_ROOT}/references/invariants.md`.
## Phase 1: Identify Feature
**Goal**: Determine feature name from current branch or argument.
1. If `$ARGUMENTS` provided, use it as feature name
2. Otherwise, extract from current branch: `git branch --show-current` (strip `feature/` prefix)
## Phase 2: Pre-finish Checks
**Goal**: Run tests before finishing.
1. Identify test commands (check package.json, Makefile, etc.)
2. Run tests if available; exit if tests fail
## Phase 3: Update Changelog
**Goal**: Document changes in CHANGELOG.md.
1. Ensure changes are in `[Unreleased]` section per `${CLAUDE_PLUGIN_ROOT}/examples/changelog.md`
2. Stage CHANGELOG.md: `git add CHANGELOG.md`
3. Determine the correct Claude model name for co-author attribution
- Valid models: Claude Sonnet 4.6, Claude Opus 4.6, Claude Haiku 4.5
4. Commit with git-agent: `git-agent commit --no-stage --intent "update changelog for feature $FEATURE_NAME" --co-author "Claude <Model> <Version> <noreply@anthropic.com>"`
5. On auth error (401), retry with `--free`
6. **Fallback** (git-agent unavailable): `git commit -m "chore: update changelog for feature $FEATURE_NAME"` with conventional format and `Co-Authored-By` footer
## Phase 4: Finish Feature
**Goal**: Complete feature using git-flow-next CLI.
1. Run `git flow feature finish $FEATURE_NAME`
2. Verify current branch: `git branch --show-current` (should be on develop)
3. Push develop: `git push origin develop`
Execute: Launch a general-purpose agent using the prompt template above