skills.rest
gewoonseba
gewoonsebaCOMMUNITY
Explore all skills by this author →
Website𝕏@sebastoelenGitHub

rename-branch

Rename the current Git branch with a conventional prefix and optional GitHub ticket reference.

9|Updated Dec 21, 2025
Search Tags:#git#workflow#rename#ticket#branch#convention
One-click install
npx skills add https://github.com/gewoonseba/dotfiles --skill rename-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rename-branch
Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/rename-branch
Command: npx skills add https://github.com/gewoonseba/dotfiles --skill rename-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rename the current git branch to follow the project's naming convention.

Core Features & Use Cases

  • Enforces branch prefixes: feat/, fix/, chore/, prototype/ based on scope.
  • Supports optional GitHub ticket references in the form <prefix>/<ticket>-<short-description>.
  • Provides a step-by-step guide to inspect the current branch, assess changes, and apply a conforming rename.

Quick Start

Rename the current branch to follow the project's naming convention.

Frequently Asked Questions about rename-branch

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

FAQPage Schema
How do I rename a git branch to follow conventional commit prefixes like feat/ or fix/?▼

To rename a git branch conventionally, the skill evaluates your current branch changes and applies the proper prefix (feat/, fix/, chore/, or prototype/) using the git branch -m command. It guides you through inspecting changes and selecting the correct scope before renaming.

What is the correct format for including a GitHub ticket reference in a git branch name?▼

The correct format for a GitHub ticket reference in a git branch name is <prefix>/<ticket>-<short-description>. The skill enforces this convention, ensuring your branch includes the appropriate prefix and ticket number for tracking.

How do I know which conventional branch prefix to use for my current changes?▼

To determine the correct conventional branch prefix, the skill assesses your current branch changes step-by-step. It evaluates whether your work fits feat/, fix/, chore/, or prototype/ scopes before applying the appropriate rename.

Can I rename a git branch without losing my uncommitted changes?▼

Yes, you can rename a git branch without losing changes. The skill inspects your current branch and evaluates modifications before renaming it with git branch -m, which safely updates the branch name without affecting your working directory.

What is the best way to fix a misnamed git branch in my development workflow?▼

The best way to fix a misnamed git branch is to enforce conventional naming standards. The skill identifies your current branch, evaluates the scope of changes, chooses the proper prefix, and renames it to follow project conventions.

Related Skills

Explore More Software Engineering Skills→
Hey-DigaHey-Diga
16

create-branch

Generate a kebab-case git branch name from uncommitted changes and create it on main.

Official
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
justinpbarnettjustinpbarnett

branch

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

Community
Intermediate