skills.rest
dennisonbertram
dennisonbertramCOMMUNITY
Explore all skills by this author →
Website𝕏@DennisonBertramGitHub

git-branching

Automate Git branching workflows with naming conventions and safety rules.

1|1|Updated Mar 6, 2026
Search Tags:#git#workflow#branching#version-control#branch-naming#git-commands
One-click install
npx skills add https://github.com/dennisonbertram/go-agent-harness --skill git-branching-dennisonbertram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-branching
Source: https://github.com/dennisonbertram/go-agent-harness/tree/main/skills/git-branching
Command: npx skills add https://github.com/dennisonbertram/go-agent-harness --skill git-branching-dennisonbertram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Branch management often suffers from inconsistent naming and unclear workflows, leading to confusion and merge conflicts.

Core Features & Use Cases

  • Branch naming conventions: enforce kebab-case with type prefixes (feature/, fix/, release/, hotfix/, worktree-agent-...).
  • Create and switch branches with recommended commands.
  • List and delete branches, keep branches up to date with upstream.
  • Safety rules to avoid pushing directly to main.

Quick Start

Create and switch to a new feature branch named feature/42-add-auth.

Frequently Asked Questions about git-branching

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

FAQPage Schema
How do I enforce consistent Git branch naming conventions for feature and bugfix workflows?▼

Standardize Git branch workflows by applying kebab-case with type prefixes like feature/, fix/, release/, and hotfix/. This standardizes branch lifecycles and reduces confusion across local and remote repositories.

What is the best way to automate Git branch creation and switching for new features?▼

Automate Git branch creation by using recommended commands to create and switch to new feature or bugfix branches. This ensures branches follow naming conventions and stay updated with upstream throughout their lifecycle.

How do I prevent accidental direct pushes to the main branch in a version control workflow?▼

Prevent direct pushes to main by applying safety rules within your Git branching workflow. These rules restrict direct commits to main and enforce the use of dedicated feature, bugfix, or hotfix branches instead.

Can I manage worktree branches alongside standard feature and release branches?▼

Yes, you can manage worktree branches alongside standard branches. The workflow supports worktree-agent- prefixed branches, applying the same naming conventions, lifecycle commands, and cleanup tasks as feature and release branches.

How do I clean up outdated Git branches and keep them synced with upstream?▼

Clean up outdated Git branches by using list and delete commands to remove merged or stale branches. Keep remaining branches up to date by syncing them with their upstream remote repositories.

Related Skills

Explore More Software Engineering Skills→
SimHackerSimHacker
49

reward

Generates context-appropriate rewards for achievements, including items, abilities, titles, and heirlooms.

Community
Basic
dyoshikawadyoshikawa
1

clean-branches

Identify and delete stale local and remote-tracking git branches.

Community
Intermediate
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
autohandaiautohandai
10

git-workflow-mastery

Configure Git branching strategies and conventional commit workflows.

Official
Advanced