af-git-branch

Create and checkout git branches with standardized kebab-case naming.

1|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/e-stpierre/agentic-forge --skill af-git-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-git-branch
Source: https://github.com/e-stpierre/agentic-forge/tree/main/src/claude/.claude/skills/git-branch
Command: npx skills add https://github.com/e-stpierre/agentic-forge --skill af-git-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce errors and inconsistency when creating git branches by enforcing a predictable naming convention, linking branches to issue identifiers when available, and avoiding interactive prompts during branch creation.

Core Features & Use Cases

  • Consistent Naming: Constructs branch names as <category>/<issue-id>_<branch-name> or <category>/<branch-name> and enforces kebab-case for readability.
  • Context Inference: Extracts category, issue IDs, and descriptive names from conversation context when arguments are incomplete.
  • Non-interactive Execution: Optionally checks out a specified base branch and runs git checkout -b to create the branch, returning structured JSON with branch details.
  • Use Case: Quickly create a feature branch tied to a GitHub issue or infer a safe branch name from a task description without manual formatting.

Quick Start

Create a new feature branch from main for issue 123 with a kebab-case name derived from the task description.

Frequently Asked Questions about af-git-branch

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

FAQPage Schema
How do I create a git branch with a consistent naming convention?

Create consistent git branches by formatting names as <category>/<issue-id>_<branch-name> or <category>/<branch-name>, enforcing kebab-case for readability. This standardized naming convention reduces errors and avoids interactive prompts during branch creation.

Can I link a new git branch to a GitHub issue automatically?

You can link git branches to issue identifiers by including an issue ID in the branch name structure. The tool extracts issue IDs from conversation context or explicit arguments, embedding them directly into the final branch name.

How do I infer a safe git branch name from a task description?

Infer safe git branch names from task descriptions by extracting category, issue IDs, and descriptive names from conversation context when arguments are incomplete. Missing values are automatically derived and formatted into kebab-case for safe shell execution.

What's the best way to automate feature branch creation without interactive prompts?

Automate feature branch creation by optionally checking out a specified base branch and running git checkout -b non-interactively. This returns structured JSON with branch details, eliminating manual formatting and interactive prompts during version control operations.

Does this git branch automation tool enforce specific category prefixes?

This git branch automation tool supports standard category prefixes like feature, fix, and chore. It applies these categories to construct standardized branch names, ensuring consistent version control practices across feature, fix, or chore topic branches.

Can I specify a base branch when creating a new topic branch?

You can specify a base branch when creating a new topic branch. The tool optionally checks out the specified base branch before running git checkout -b, ensuring new branches are created from the correct version control starting point.