skills.rest
constellos
constellosOFFICIAL
Explore all skills by this author →
Website𝕏@constellosaiGitHub

Branch Orchestration

Generate Git branch names from issue context and link them to GitHub issues.

5|3|Updated Nov 30, 2025
Search Tags:#git#github#branch#workflow-automation#branch-naming#issue-linking#work-type
One-click install
npx skills add https://github.com/constellos/claude-code-plugins --skill branch-orchestration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Branch Orchestration
Source: https://github.com/constellos/claude-code-plugins/tree/main/plugins/github-orchestration/skills/branch-orchestration
Command: npx skills add https://github.com/constellos/claude-code-plugins --skill branch-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch naming and issue linkage are often manual and error-prone. This skill automates consistent branch creation, renaming, linking to GitHub issues, and lifecycle management.

Core Features & Use Cases

  • Intelligent branch naming following the convention {issueNum}-{workType}/{kebab-name} to ensure traceability.
  • Automatic linking of branches to GitHub issues to keep references up-to-date.
  • Branch lifecycle management including creation, renaming, remote synchronization, and cleanup across a project.
  • Work type detection from issue title and labels to classify branches automatically.

Quick Start

Install Git and the GitHub CLI, then in your repository run a sample to generate and create a branch:

  • Generate a branch name: BRANCH_NAME=$(generateBranchName 42 "feature" "Add dark mode")
  • Create and push: git checkout -b "$BRANCH_NAME"; git push -u origin "$BRANCH_NAME" You can also switch to the correct branch using issue context and ensure it is linked to the corresponding GitHub issue.

Frequently Asked Questions about Branch Orchestration

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

FAQPage Schema
How do I automate Git branch naming and issue linking?▼

You can automate Git branch naming and issue linking by applying a convention that detects work type from GitHub issue data, generating names like `{issueNum}-{workType}/{kebab-name}` to ensure traceability.

Do I need the GitHub CLI installed to link branches to issues?▼

Yes, you need both Git and the GitHub CLI installed locally to automatically link branches to GitHub issues and fetch the issue context required for intelligent branch lifecycle management.

What is the best way to manage Git branch lifecycle and cleanup across projects?▼

The best way to manage Git branch lifecycle is to automate creation, renaming, remote synchronization, and cleanup using issue context, storing branch-to-issue mappings in a local JSON log file.

How does work type detection from GitHub issues work for branch naming?▼

Work type detection reads the GitHub issue title and labels to automatically classify the branch, integrating the detected work type directly into the standardized branch naming pattern.

Where are branch-to-issue mappings stored when automating Git branch workflows?▼

Branch-to-issue mappings are stored in a local JSON file at `.claude/logs/branch-issues.json`, persisting the link between your generated Git branches and their corresponding GitHub issues.

Related Skills

Explore More Software Engineering Skills→
BinkyTwinBinkyTwin
1

github-cli

Automate GitHub issues and pull requests via the gh CLI with conventional commits.

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
usk6666usk6666
11

implement

Automate software development from Linear issues to pull request creation.

Community
Advanced
cruzanstxcruzanstx
6

worktree

Create and manage git worktrees for isolated development environments.

Community
Advanced