branch

Creates a Git branch named from a GitHub issue's title and number.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill branch-ryan-mahoney
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/branch
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill branch-ryan-mahoney

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branching from issues is error-prone and slows down development. This skill automates creating a descriptive local branch tied to a GitHub issue to improve traceability and start-work efficiency.

Core Features & Use Cases

  • Automates creation of a feature/bugfix branch named from the issue topic and number.
  • Checks out the new branch and reports its name to the user.
  • Supports standard git workflows and quick issue-to-branch handoffs.

Quick Start

Create a new local branch from GitHub issue #123 and switch to it.

Frequently Asked Questions about branch

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

FAQPage Schema
How do I create a git branch from a GitHub issue automatically?

Creating a git branch from a GitHub issue is automated by generating a descriptive branch name derived from the issue topic and number, then checking out the new local branch to start feature development immediately.

What is the best way to automate issue-driven git checkout for feature development?

Automating issue-driven git checkout is best handled by deriving a local branch name directly from the GitHub issue topic, ensuring traceability and improving start-work efficiency for standard git workflows.

Do I need a specific repository context to generate a branch from GitHub issues?

Yes, you need a repository context and a GitHub issue number to generate a descriptive local branch name and automatically check out the new branch for your dev workflow.

How does tying a local git branch to an issue number improve traceability?

Tying a local git branch to an issue number improves traceability by automatically generating a descriptive branch name from the GitHub issue topic, linking your feature development directly to the issue context.

Why does manual branching from GitHub issues slow down development workflows?

Manual branching from GitHub issues slows down development because it is error-prone, whereas automating the creation of a descriptive local branch tied to the issue improves start-work efficiency and traceability.