ReddRadar
Agent skill
branch-name
When naming Git branches, provide guidelines on the recommended branch naming conventions for the project.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/branch-name
SKILL.md
Basic Policy
- Prioritize branch names that clearly indicate their purpose at a glance
- Use a structure of prefix +
/+ identifier - Use lowercase and kebab-case for the identifier
- Do not use characters other than alphanumeric and allowed symbols
Prefix List
feat: Add new featuresfix: Fix bugs in existing featureshotfix: Urgent fixes that need immediate deploymentrefactor: Refactoring without changing functionalitychore: Non-functional tasks such as dependency updates and CI configuration adjustmentsdocs: Adding or modifying documentation (not related to functionality)test: Adding or modifying test code (not related to functionality)release: Release preparation tasks
Identifier Naming Rules
- Keep branch names short and meaningful
- Connect words using kebab-case
- Include the issue number at the beginning if the branch is based on an issue
- Write identifiers in English
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
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?