skills.rest
nickcorin
nickcorinCOMMUNITY
Explore all skills by this author →
𝕏@maxxedgoofGitHub

git-branch

Enforce consistent Git branch naming with context and issue-number templates.

2|Updated Feb 27, 2020
Search Tags:#git#branching#naming-conventions#branch-management#pull-request#version-control
One-click install
npx skills add https://github.com/nickcorin/dotfiles --skill git-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-branch
Source: https://github.com/nickcorin/dotfiles/tree/main/dot_config/opencode/skill/git-branch
Command: npx skills add https://github.com/nickcorin/dotfiles --skill git-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistent branch naming reduces confusion and speeds up code reviews by making branch purpose clear.

Core Features & Use Cases

  • Enforces a naming convention: <context>/[issue-number-]<short-description>.
  • Documents allowed contexts (chore, doc, feat, fix, ref, rfc, release) and provides practical examples.
  • Supports standard Git workflows by guiding branch creation and PR review processes.

Quick Start

Create a new branch using the naming convention <context>/[issue-number-]<short-description> and open a pull request for review.

Frequently Asked Questions about git-branch

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

FAQPage Schema
What's the best way to name git branches for features and bug fixes?▼

Yes, you can enforce standard branch naming conventions for release branches by using the <context>/[issue-number-]<short-description> template. This approach standardizes release branch creation and integrates seamlessly into pull request-based code review workflows.

How do I include an issue number when creating a git branch?▼

To include an issue number in git branch creation, place it after the context and before the short description, such as feat/123-add-login. This naming template reduces confusion and links branch changes directly to tracked issues during PR reviews.

Why does consistent git branch naming matter for pull request workflows?▼

Consistent git branch naming matters because it reduces confusion and speeds up pull request workflows by making branch purpose clear. Applying a defined naming template with allowed contexts helps reviewers immediately identify the type of change being proposed.

Does this branch naming approach support refactoring and documentation tasks?▼

Yes, this branch naming approach supports refactoring and documentation tasks by including ref and doc as allowed contexts. You can create branches like ref/456-simplify-auth or doc/update-readme to maintain clear version control management across various task types.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-git-initialize

Initialize a Git repository with configurable branch and .gitignore settings.

Community
Intermediate
JacobPEvansJacobPEvans
3

sync-main

Fetch remote main updates and merge them into the current branch.

Community
Intermediate
mauriciodelriomauriciodelrio
3

git-usage

Enforces Git commit message, branch naming conventions via commitlint and Husky.

Community
Advanced
luanluan
4

start

Create a Git branch and link it to a beads issue.

Community
Intermediate