From git-flow
Create a new Git Flow feature branch from develop with proper naming and tracking
npx claudepluginhub abhattacherjee/claude-code-skills --plugin git-flow<feature-name># Git Flow Feature Branch Create new feature branch: **$ARGUMENTS** ## Current Repository State - Current branch: !`git branch --show-current` - Git status: !`git status --porcelain` - Develop branch status: !`git log develop..origin/develop --oneline 2>/dev/null | head -5 || echo "No remote tracking for develop"` ## Task Create a Git Flow feature branch following these steps: ### 1. Pre-Flight Validation - **Check git repository**: Verify we're in a valid git repository - **Validate feature name**: Ensure `$ARGUMENTS` is provided and follows naming conventions: - Valid: `user-auth...
/featureOrchestrates full feature development cycle: PRD with product-owner, visual style options, architecture, code, QA, docs, delivery via phased agents and gates.
/featureAutomates Rails feature/chore from Linear URL or description: creates branch, gathers context, implements/tests/lints/i18n, drafts PR, monitors CI.
/featureCreates a lightweight feature-focused PRD via guided interactive interview (5-8 rounds) optimized for new features in existing products, saving to docs/prd/{slug}.md
/featureExecutes Mermaid flowchart workflow: two Analyze-Design(D3)-Develop(G2→G2.5→G3)-Release cycles, using Task for sub-agents, AskUserQuestion at diamonds, and F5 gates.
/featureGuides through 10-stage new feature development workflow from brainstorming to code review, pausing for user confirmation at each stage.
/featureImplements features from Linear/Jira issues or prompts using minimal iteration cycles and structured workflow with resume detection, producing code increments, tests, reviews, and PRs. Accepts [issue-key-or-prompt] [--provider=linear|jira|prompt] [--silent=true|false].
Create new feature branch: $ARGUMENTS
git branch --show-currentgit status --porcelaingit log develop..origin/develop --oneline 2>/dev/null | head -5 || echo "No remote tracking for develop"Create a Git Flow feature branch following these steps:
$ARGUMENTS is provided and follows naming conventions:
user-authentication, payment-integration, dashboard-redesignfeat1, My_Feature, empty namedevelop branch is present# Switch to develop branch
git checkout develop
# Pull latest changes from remote
git pull origin develop
# Create feature branch with Git Flow naming convention
git checkout -b feature/$ARGUMENTS
# Set up remote tracking
git push -u origin feature/$ARGUMENTS
After successful creation, display:
Feature Branch Ready
Branch: feature/$ARGUMENTS
Base: develop
Status: Clean working directory
Next Steps:
1. Start implementing your feature
2. Make commits using conventional format:
git commit -m "feat: your changes"
3. Add CHANGELOG entries under [Unreleased] — never assign a version number on feature branches
4. Push changes regularly: git push
5. When complete, use /finish to merge back to develop
Feature Name Not Provided:
Feature name is required
Usage: /feature <feature-name>
Examples:
/feature user-profile-page
/feature api-v2-integration
Feature names should be kebab-case and descriptive.
Branch Already Exists:
Branch feature/$ARGUMENTS already exists
Options:
1. Switch to existing branch: git checkout feature/$ARGUMENTS
2. Use a different feature name
3. Delete existing and recreate (destructive!)
Uncommitted Changes:
You have uncommitted changes:
[list files]
Options:
1. Commit changes first
2. Stash changes: git stash
3. Discard changes: git checkout .
No Develop Branch:
Develop branch not found
Git Flow requires a 'develop' branch. Create it with:
git checkout -b develop
git push -u origin develop
See the git-flow skill for the full branching model, conventions, and gotchas.
Feature branches: develop -> feature/<name> -> develop (no tag). Use /finish to merge.
/finish — Complete and merge feature branch to develop/flow-status — Check current Git Flow status/release <version> — Create release branch from develop/hotfix — Create hotfix branch from maingit-flow skill — Branching model reference, conventions, and diagnostic script