git-worktree

Automate Git worktree creation, commits, PRs, and cleanup for feature branches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kimny1143/mued_v2 --skill git-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree
Source: https://github.com/kimny1143/mued_v2/tree/main/.claude/skills/git-worktree
Command: npx skills add https://github.com/kimny1143/mued_v2 --skill git-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides disciplined Git worktree usage to keep main branch clean and manage feature work efficiently.

Core Features & Use Cases

  • Worktree workflow: Automatically generate and manage temporary worktrees, prune stale worktrees, and keep main clean.
  • Branch strategy: Enforce a simple main/feature/fix/hotfix scheme.
  • PR/merge guidance: Guidelines for PR creation and merging from worktrees.

Quick Start

Create a new worktree for a feature: git worktree add ~/.claude-worktrees/mued_v2/feature-xxx -b feature/xxx

Frequently Asked Questions about git-worktree

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

FAQPage Schema
How do I manage multiple feature branches without cluttering my main repository?

Git worktree management creates isolated temporary worktrees for each feature branch, keeping your main directory clean while allowing parallel development. Each worktree operates independently, so you can switch between features without stashing or checking out repeatedly.

What's the best workflow for creating and merging feature branches with pull requests?

Create a worktree for your feature branch using `git worktree add`, develop and commit changes, trigger an automated PR creation and review, then merge validated changes into main. After merge, the worktree is automatically cleaned up.

Can I use git worktree for fix and hotfix branches, or just features?

Git worktree supports a main/feature/fix/hotfix branch structure, so you can create isolated worktrees for all three types. Each follows the same lifecycle from creation through PR review to cleanup.

How do I clean up stale worktrees and keep my workflow efficient?

Prune stale worktrees automatically and use post-session cleanup hooks to propose deletions of abandoned branches. Listing and removing commands let you manage the full worktree lifecycle without manual overhead.

Do I need approval for all changes, or can documentation-only updates skip the PR process?

Code and configuration changes require PR approval and merge validation, but documentation-only changes are optional for PR review. This balances governance with development velocity.