git-worktree-manager

Create, list, switch, and clean up Git worktrees with safety checks.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/gar-ai/mallorn --skill git-worktree-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-worktree-manager
Source: https://github.com/gar-ai/mallorn/tree/main/.claude/skills/git-worktree-manager
Command: npx skills add https://github.com/gar-ai/mallorn --skill git-worktree-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers juggling multiple feature branches often end up with cluttered workflows and manual, error-prone setup when coordinating several worktrees.

Core Features & Use Cases

  • Create and manage multiple Git worktrees for concurrent feature development.
  • Open each worktree in its own terminal or editor to keep work contexts separate.
  • List, switch between, and clean up worktrees with safety checks and Git integrity.

Quick Start

Run the scripts to create a feature worktree and automatically open it in Claude Code or VSCode.

Frequently Asked Questions about git-worktree-manager

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

FAQPage Schema
How do I manage Git worktrees for parallel feature development without manual setup?

Git worktree management scripts automate creating multiple worktrees for parallel features, opening each in a dedicated terminal or editor to keep work contexts separate. This eliminates cluttered workflows and error-prone manual coordination when juggling feature branches.

Can I open a Git worktree in VSCode or Claude Code automatically?

Yes, Git worktree scripts can automatically open newly created worktrees in VSCode or Claude Code. This keeps each parallel feature development context isolated in its own editor window, preventing workspace overlap.

How do I switch between Git worktrees and clean them up safely?

CLI scripts list active Git worktrees and allow switching between them, while interactive cleanup performs safety checks and verifies Git integrity before removal. This prevents accidental data loss when managing multiple parallel feature branches.

What is the best way to handle parallel development across multiple Git branches?

Using Git worktrees is the best way to handle parallel development, allowing you to checkout multiple branches simultaneously in separate directories. Automated scripts streamline creating, opening, and cleaning up these worktrees to maintain isolated workspaces.

Do I need any dependencies to use Git worktree scripts for terminal workspace management?

No external dependencies are required to use these Git worktree scripts for terminal workspace management. The scripts operate independently to create, list, switch, and clean up worktrees with built-in Git integrity safety checks.