branch

Create Git branches and worktrees with enforced naming conventions.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill branch-mj-agentlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-git/skills/mj-git-branch
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill branch-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of creating, naming, and managing Git branches and worktrees according to established project strategies, reducing complexity and potential errors in version control workflows.

Core Features & Use Cases

  • Branch Creation: Generates feature, bugfix, documentation, maintain, and hotfix branches.
  • Worktree Management: Sets up and removes Git worktrees for isolated development.
  • Branch Naming: Enforces consistent naming conventions based on branch type and task description.
  • Use Case: When starting a new feature, you can instruct the AI to create a feature/user-auth branch from develop, and it will handle the necessary Git commands and worktree setup.

Quick Start

Create a new feature branch named 'add-user-authentication' from the develop branch.

Frequently Asked Questions about branch

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

FAQPage Schema
How do I create a new Git branch for a feature from the develop branch?

To create a Git branch for a feature, you specify the branch type and description, such as instructing the AI to create 'feature/user-auth' from 'develop', which then handles the necessary Git commands and worktree setup automatically.

How does Git worktree management work for isolated development?

Git worktree management sets up and removes isolated working directories from a bare repository, allowing you to manage multiple branches simultaneously without switching contexts in a single working directory.

What is the best way to enforce consistent Git branch naming conventions?

Enforcing consistent Git branch naming conventions requires categorizing branches by type, such as feature, bugfix, documentation, maintain, or hotfix, and generating names based on the specific task description.

Can I set up a Git worktree for a bare repository?

Yes, you can set up Git worktrees for bare repositories, which enables isolated development environments and allows multiple branches to be checked out simultaneously across different directories.

What types of development workflows support dedicated Git branches?

Dedicated Git branches support various development workflows including feature development, bugfixes, documentation updates, maintenance tasks, and hotfixes, streamlining version control for each specific scenario.