branch

Create descriptive git branch names from session context and validate them.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill whenever the user wants to CREATE or SET UP a new git branch. This includes any request to generate a branch name, start a new branch, check out a fresh branch, or begin work that requires branching. Covers explicit requests ("create a branch", "new branch", "branch for this") and implicit ones ("set up a branch for X", "start working on X" when no branch exists).

Core Features & Use Cases

  • Automatically derive branch names from active tasks, context, and user input to create descriptive, predictable branches.
  • Validate naming conventions and guardrails before creating the branch to avoid conflicts and invalid refs.
  • Confirm with the user prior to creation and handle edge cases like existing branches or non-repository contexts.

Quick Start

Ask me to create a descriptive branch for my current task.

Frequently Asked Questions about branch

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

FAQPage Schema
How do I create a descriptive git branch automatically from my current task context?

To create a descriptive git branch automatically, this skill derives branch names from active tasks, project conventions, and git state, validating naming rules and confirming with you before creation.

What is the best way to generate git branch names that follow project naming conventions?

Generating git branch names compliant with project conventions requires validating rules against existing refs. This skill automates validation by deriving compliant branch names from session context to prevent invalid refs.

Can I use context-aware branching to handle existing branches or non-repository scenarios?

Yes, context-aware branching can handle existing branches and non-repository scenarios. This skill detects branch conflicts and manages non-repository contexts gracefully before attempting creation.

How do I validate git branch naming rules before checking out a new branch?

Validating git branch naming rules before checkout involves checking guardrails and existing refs. This skill validates conventions and handles edge cases before creating and checking out your branch.

Does git branch automation work without manually specifying a branch name?

Git branch automation works without manual names by deriving descriptive branch names from active tasks and user input. It uses session context to produce predictable, compliant branch names automatically.