ia-git-worktree

Manage Git worktrees for isolated parallel development via worktree-manager.sh.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-git-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia-git-worktree
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-git-worktree
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-git-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents messy, error-prone parallel development by making it consistent and safer to create, review, and clean up isolated Git worktrees with the right environment setup.

Core Features & Use Cases

  • Isolated parallel development: Create worktrees for feature branches or PR reviews without contaminating your main working tree, so concurrent tasks stay separated.
  • Safe, repeatable setup: Uses a dedicated manager script instead of direct git worktree commands, including copying relevant .env files and ensuring .worktrees is ignored.
  • Operational workflows: Supports common day-to-day actions like listing worktrees, switching/go-ing into an existing one, copying env files, and interactively cleaning up inactive worktrees.
  • Safety and guardrails: Documents and enforces safety verification patterns (including checking .gitignore coverage) and provides structured guidance for completing review work.

Quick Start

Ask the AI to run the worktree manager to create a new isolated worktree for branch pr-123-feature-name so you can review that change in parallel.

Frequently Asked Questions about ia-git-worktree

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

FAQPage Schema
How do I manage Git worktrees for parallel development without contaminating my main branch?

Git worktrees allow isolated parallel development by creating separate working directories for feature branches or PR reviews. Using a dedicated manager script ensures consistent environment setup and prevents contamination of your main working tree.

What is the best way to set up environment files when creating a new Git worktree?

When creating a Git worktree, you should copy relevant .env files into the new working directory. A dedicated worktree manager script automates this environment setup, ensuring the isolated branch has the necessary configuration.

Can I review pull requests in parallel using Git worktrees?

Yes, Git worktrees are ideal for code review workflows. You can create an isolated worktree for a specific PR branch, review the changes in a separate working directory, and safely clean it up afterward without affecting your primary workspace.

How do I safely clean up inactive Git worktrees and remove their branches?

Safely cleaning up Git worktrees requires interactively removing inactive directories and verifying that .worktrees is properly ignored in .gitignore. The worktree manager script provides structured cleanup commands to handle this process.

Why should I use a script instead of direct git worktree commands for branch management?

Using a dedicated script instead of direct git worktree commands ensures safety and repeatability. It enforces guardrails like validating .gitignore coverage and copying .env files, which prevents error-prone manual setup during parallel branch development.

Does Git worktree management work for concurrent feature development on the same repository?

Yes, Git worktrees support concurrent feature development by providing separate work directories for each branch. This approach keeps concurrent tasks separated and maintains stability without needing multiple repository clones.