branch-naming

Included with Lifetime

$97 forever

# Branch Naming Skill

General

What this skill does

# 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`

Files: 1

Size: 1.8 KB

Complexity: 3/100

Category: General

Source: https://github.com/poindexter12/claude-flow/tree/main/skills/branch-naming

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts