Agent skill

branch-naming

Stars 0
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/poindexter12/claude-flow/tree/main/skills/branch-naming

SKILL.md

Branch Naming Skill

Generate consistent, readable branch names from descriptions.

Prefixes align with the conventional-commit skill types for a unified workflow.

Format

[prefix/]short-descriptive-name

Prefixes

Match conventional commit types for consistency:

Prefix Commit Type Use When
feat/ feat: New functionality
fix/ fix: Bug fixes
docs/ docs: Documentation only
style/ style: Formatting, no code change
refactor/ refactor: Code restructuring
perf/ perf: Performance improvements
test/ test: Adding/fixing tests
chore/ chore: Maintenance, deps, config

Use a prefix when the intent is clear. Skip it if ambiguous.

Rules

  1. Kebab-case: lowercase, hyphens between words (add-user-auth)
  2. Short: 3-5 words max, under 50 chars total
  3. Descriptive: what it does, not how (add-search not implement-elasticsearch)
  4. No fluff: drop articles and filler (user-profile not the-user-profile-page)
  5. No ticket numbers alone: fix/login-timeout not just JIRA-1234

Examples

Description Branch Name
"Add user authentication" feat/add-user-auth
"Fix the login timeout bug" fix/login-timeout
"Update README with install instructions" docs/update-readme
"Refactor the payment processing module" refactor/payment-processing
"Bump lodash to fix security issue" chore/bump-lodash
"Quick experiment with caching" try-caching

Edge Cases

  • Ticket numbers: Include after prefix if team uses them: feat/PROJ-123-add-search
  • Uncertain scope: Skip prefix, use descriptive name: improve-performance
  • Spikes/experiments: Use try- or spike- prefix: try-redis-caching

Expand your agent's capabilities with these related and highly-rated skills.

poindexter12/claude-flow

conventional-commit

Generate commit messages by analyzing git diff following Conventional Commits format. Use when user says "commit", "commit my changes", "write a commit message", "what should I commit as", needs help describing changes, or is about to commit without a message.

0 0
Explore
mattpocock/skills

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

111,310 9,758
Explore
mattpocock/skills

handoff

Compact the current conversation into a handoff document for another agent to pick up.

111,310 9,758
Explore
mattpocock/skills

scaffold-exercises

Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

111,310 9,758
Explore
mattpocock/skills

edit-article

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

111,310 9,758
Explore
mattpocock/skills

git-guardrails-claude-code

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

111,310 9,758
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results