Agent skill
create-feature-branch
Create a new feature branch following Git Flow strategy. Use when starting new feature development, creating a branch for an issue, or when user says "create branch", "new feature", "start working on issue".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/create-feature-branch-tettuan-breakdown-ea12c5c9
SKILL.md
Create Feature Branch
This skill creates feature branches following the project's Git Flow strategy.
Branch Naming Convention
| Prefix | Purpose | Example |
|---|---|---|
feat/ |
New feature | feat/issue-88-return-mode |
fix/ |
Bug fix | fix/stdout-encoding |
refactor/ |
Refactoring | refactor/output-processor |
update/ |
Dependency updates | update/jsr-packages |
remove/ |
Feature removal | remove/deprecated-api |
Workflow
1. Ensure clean working directory
git status
If there are uncommitted changes, ask user how to handle them.
2. Update develop branch
git checkout develop
git pull origin develop
3. Create feature branch
Format: {prefix}/issue-{number}-{short-description}
git checkout -b feat/issue-{NUMBER}-{DESCRIPTION}
4. Confirm creation
git branch --show-current
Checklist
- Working directory is clean
- develop branch is up to date
- Branch name follows convention
- Branch is created from develop
Example
For Issue #88 (add return mode):
git checkout develop
git pull origin develop
git checkout -b feat/issue-88-return-mode
Notes
- Always branch from
develop, notmain - Include issue number in branch name for traceability
- Use lowercase with hyphens for descriptions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?