multiAI Summary Pending
worktree-manager-skill
Comprehensive git worktree management. Use when the user wants to create, remove, list, or manage worktrees. Handles all worktree operations including creation, deletion, and status checking.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/worktree-manager-skill/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/egadams/worktree-manager-skill/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/worktree-manager-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How worktree-manager-skill Compares
| Feature / Agent | worktree-manager-skill | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive git worktree management. Use when the user wants to create, remove, list, or manage worktrees. Handles all worktree operations including creation, deletion, and status checking.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Worktree Manager Skill Complete worktree lifecycle management for parallel development environments with isolated ports, databases, and configuration. ## When to use this skill Use this skill when the user wants to: - **Create** a new worktree for parallel development - **Remove** an existing worktree - **List** all worktrees and their status - **Check** worktree configuration or status - **Manage** multiple parallel development environments **Do NOT use this skill when:** - User asks for a specific subagent or skill delegation - User wants to manually use git commands directly - The task is unrelated to worktree management ## Operations Overview This skill manages three core worktree operations: | Operation | Command | When to Use | |-----------|---------|-------------| | **Create** | `/create_worktree` | User wants a new parallel environment | | **List** | `/list_worktrees` | User wants to see existing worktrees | | **Remove** | `/remove_worktree` | User wants to delete a worktree | ## Decision Tree: Which Command to Use ### 1. User wants to CREATE a worktree **Keywords:** create, new, setup, make, build, start, initialize **Action:** Use `/create_worktree <branch-name> [port-offset]` ### 2. User wants to LIST worktrees **Keywords:** list, show, display, what, which, status, check, view **Action:** Use `/list_worktrees` ### 3. User wants to REMOVE a worktree **Keywords:** remove, delete, cleanup, destroy, stop, kill, terminate **Action:** Use `/remove_worktree <branch-name>` ## Quick Start For step-by-step operation instructions, see [OPERATIONS.md](OPERATIONS.md). For detailed examples and usage patterns, see [EXAMPLES.md](EXAMPLES.md). For troubleshooting and common issues, see [TROUBLESHOOTING.md](TROUBLESHOOTING.md). For technical details and quick reference, see [REFERENCE.md](REFERENCE.md). ## Important Notes ### Do NOT attempt to: - Create worktrees manually with git commands - Manually configure ports or environment files - Use bash to remove directories directly - Manage worktree processes manually ### Always use the slash commands because they: - Handle all configuration automatically - Ensure port uniqueness - Validate operations - Provide comprehensive error handling - Clean up properly on removal