branch

Create and checkout Git feature branches from spec files or names.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of new Git branches, ensuring they follow standard naming conventions and are based on the latest remote code, streamlining your development workflow.

Core Features & Use Cases

  • Automated Branch Naming: Generates branches from spec file names or direct input, applying prefixes like feat/, fix/, etc.
  • Base Branch Detection: Automatically identifies and uses the correct base branch (e.g., main or master) from your remote repository.
  • Use Case: When starting a new feature described in specs/feat-add-user-profile.md, you can simply ask the AI to "create a branch for this spec," and it will create feat/add-user-profile from your main branch.

Quick Start

Use the branch skill to create a new feature branch named 'feat/user-login' from the main branch.

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 feature branch from a spec file?

To create a Git feature branch from a spec file, provide the spec file path to the branch skill, and it will automatically parse the filename, apply conventional prefixes like feat/, and checkout the new branch from the latest remote base branch.

How do I ensure my Git branches are based on the latest remote main branch?

To ensure your Git branches are based on the latest remote main branch, the branch skill automatically detects your remote base branch and performs checkout operations directly from the updated remote source, preventing stale code merges.

Can I automatically apply conventional naming prefixes to my Git branches?

Yes, you can automatically apply conventional naming prefixes to your Git branches by passing a direct branch name or spec file path, which the tool validates against standard prefixes like feat/ and fix/.

Does this branching tool work without installing additional Git dependencies?

Yes, this branching tool works without installing additional dependencies, as it operates by automating standard Git operations directly through your AI assistant using its internal references.

What is the best way to automate Git branch creation for new features?

The best way to automate Git branch creation for new features is to ask your AI assistant to create a branch for a specific spec, which handles input parsing, naming validation, and remote base detection automatically.

Why do my Git feature branches fail validation during automated checkout?

Git feature branches fail validation during automated checkout if the input branch name does not match conventional prefixes like feat/ or fix/, which the tool strictly enforces before performing any Git operations.