branch-strategy
Branch Strategy
Branch Naming Conventions
Every branch name must follow a structured prefix convention. This keeps the repository navigable, enables CI/CD automation, and makes intent immediately clear.
Required Prefixes
| Prefix | Purpose | Example |
|---|---|---|
feature/ |
New functionality or capability | feature/user-avatar-upload |
fix/ |
Bug fixes for existing behavior | fix/login-redirect-loop |
hotfix/ |
Urgent production fixes | hotfix/payment-null-pointer |
release/ |
Release preparation and stabilization | release/2.4.0 |
chore/ |
Maintenance, dependencies, tooling | chore/upgrade-eslint-9 |
docs/ |
Documentation-only changes | docs/api-authentication-guide |
refactor/ |
Code restructuring without behavior change | refactor/extract-billing-service |
test/ |
Adding or fixing tests only | test/payment-edge-cases |
experiment/ |
Exploratory work, not intended for merge | experiment/graphql-federation |
More from claude-code-community-ireland/claude-code-resources
design-ui
This skill should be used when the user asks to "design a UI", "create a landing page", "build a dashboard", "generate a website design", "make a product page", or needs guidance on UI design patterns, accessibility standards, design tokens, or eliminating generic AI-generated design patterns (vibe-code).
12security-review
Security review checklist covering OWASP Top 10, authentication, authorization, input validation, secrets management, and common vulnerability patterns. Reference when reviewing code for security.
7design-patterns
Reference library of proven UI design patterns, component templates, and sector-specific conventions for high-quality design generation.
6architecture-decision-record
ADR format and methodology for documenting significant technical decisions with context, alternatives considered, and consequences. Use when making or documenting architectural decisions.
5pr-description
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
4refactoring-patterns
Safe refactoring techniques — extract method, rename, move, inline, and structural patterns. Includes code smell identification and transformation recipes. Use when refactoring code or improving structure.
4