skills.rest
forrestthewoods
forrestthewoodsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

branch-naming

Enforce branch names starting with issue numbers and optional Claude session prefixes.

Updated Feb 2, 2025
Search Tags:#git#workflow#claude#issues#branch#naming#branch-naming
One-click install
npx skills add https://github.com/forrestthewoods/anubis --skill branch-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-naming
Source: https://github.com/forrestthewoods/anubis/tree/main/.claude/skills/branch-naming
Command: npx skills add https://github.com/forrestthewoods/anubis --skill branch-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch naming consistency is essential for tracking work against issues, enabling automated status checks, and supporting the issue-review workflow. This skill codifies a standard pattern and provides guidance to ensure every new branch conveys its purpose and scope.

Core Features & Use Cases

  • Standard pattern: <issue-number>-<short-description> to tie branches to issues.
  • Claude session prefixes: claude/<issue-number>-<short-description>-<session-id> for session-specific work.
  • Status-aware workflows: supports issue-review integration by enabling visibility of branch state and linked PRs.

Quick Start

Name your next branch using the standard pattern that starts with the issue number.

Frequently Asked Questions about branch-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent git branch naming that links to issues?▼

To enforce consistent git branch naming, you should start branch names with the issue number followed by a short description using the <issue-number>-<short-description> pattern. This links work directly to tracked issues.

What is the standard branch naming pattern for issue tracking?▼

The standard branch naming pattern for issue tracking is <issue-number>-<short-description>. This ensures every new branch conveys its purpose and scope while tying directly to a specific issue number.

Can I include a Claude session ID in my git branch name?▼

Yes, you can include a Claude session ID in your git branch name using the claude/<issue-number>-<short-description>-<session-id> pattern. This supports session-specific collaborative work and issue tracking.

How does branch naming support issue-review workflows?▼

Branch naming supports issue-review workflows by enabling visibility of branch state and linked pull requests. Starting branch names with issue numbers allows automated status checks to track progress against issues.

Do I need any specific git extensions to track branch status via naming?▼

No specific git extensions are required to track branch status via naming. The skill provides guidance for status-aware workflows using standard branch naming conventions linked to issue numbers.

Why should branch names start with the issue number instead of a description?▼

Branch names should start with the issue number to ensure consistent tracking against issues and enable automated status checks. This pattern maintains clear linkage between branches and their corresponding issues.

Related Skills

Explore More Software Engineering Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
CodenburgCodenburg

branch-pr

Validate pull requests against approved issues and branch naming conventions.

Community
Intermediate
jporrejporre
6

b10-ship

Orchestrate GitHub issue workflows from triage through code review.

Community
Advanced
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced