skills.rest
sendo-kakeru
sendo-kakeruCOMMUNITY
Explore all skills by this author →
GitHub

branch-name

Analyze staged Git diffs to generate compliant branch name options.

Updated Aug 27, 2026
Search Tags:#git#workflow#branch#naming-conventions#staged-changes#branch-name#git-diff
One-click install
npx skills add https://github.com/sendo-kakeru/family-photo --skill branch-name
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-name
Source: https://github.com/sendo-kakeru/family-photo/tree/main/.claude/skills/branch-name
Command: npx skills add https://github.com/sendo-kakeru/family-photo --skill branch-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes the currently staged changes and suggests branch names that conform to the repository's naming conventions, freeing you from manual naming guesswork.

Core Features & Use Cases

  • Analyze the git diff --cached to infer the most suitable branch prefixes (feature/, bugfix/, hotfix/, docs/, etc.) based on the change type.
  • Generate multiple compliant branch-name options to accelerate alignment with team workflows.
  • Provide guidance on selecting the final branch name according to the project's README conventions.

Quick Start

Analyze the staged changes and generate multiple compliant branch-name suggestions that adhere to the project's naming rules.

Frequently Asked Questions about branch-name

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

FAQPage Schema
How do I generate a git branch name from staged changes?▼

To generate a git branch name from staged changes, the Skill parses your git diff --cached output, infers appropriate prefixes like feature/*, bugfix/*, hotfix/*, or docs/* based on the modification type, and produces multiple compliant naming options.

What is the best way to ensure my branch naming conventions match my repository rules?▼

The best way to ensure branch naming conventions match repository rules is to consult your project's README.md documentation. The Skill analyzes staged diffs and references these documented conventions to guarantee the suggested branch names satisfy your specific naming rules.

Can I get multiple branch name suggestions for different git workflows like hotfix and feature?▼

Yes, you can get multiple branch name suggestions for different git workflows. The Skill applies to feature development, bug fixes, and maintenance workflows, generating various options that align with prefixes such as feature/*, bugfix/*, hotfix/*, and docs/*.

Does the branch naming tool require any external dependencies or components to run?▼

No, the branch naming tool does not require any external dependencies or components to run. It operates standalone to analyze your staged git diffs and repository conventions to output compliant branch names without additional packages.

Why does my suggested branch name not match my project documentation?▼

If a suggested branch name does not match your project documentation, ensure your README.md clearly defines the naming rules. The Skill consults the repository conventions documented in the README.md to guide the final selection and ensure naming compliance.

Related Skills

Explore More Software Engineering Skills→
maggitmaggit

commit

Generate conventional commit messages from staged Git changes.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
joaquimscostajoaquimscosta
21

creating-branch

Create standardized Git feature branches with incrementing names.

Community
Advanced