use-worktrees

Create isolated Git worktrees for feature development with setup and baseline validation.

1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/mtthsnc/autonome --skill use-worktrees
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-worktrees
Source: https://github.com/mtthsnc/autonome/tree/main/skills/use-worktrees
Command: npx skills add https://github.com/mtthsnc/autonome --skill use-worktrees

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting feature work directly in the main workspace risks contaminating the current state, leaking context, and complicating reviews. This skill provides a safe isolation strategy using Git worktrees to separate concurrent work streams.

Core Features & Use Cases

  • Create and manage isolated worktrees for feature development, enabling parallel work without switching branches.
  • Respect project-local or global preferences (e.g., CLAUDE.md guidance) and verify safety checks before creation.
  • Automate the setup and baseline verification to ensure a clean starting point for new work.

Quick Start

Initialize an isolated feature workspace by creating and configuring a dedicated Git worktree.

Frequently Asked Questions about use-worktrees

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

FAQPage Schema
How do I isolate feature development in Git without altering my current workspace?

Git worktrees create isolated working directories for feature development, allowing parallel branch work without contaminating the main workspace or switching branches. This skill automates worktree creation, setup, and baseline verification.

What's the best way to manage concurrent feature branches in a single repository?

Git worktrees provide a safe isolation strategy for concurrent feature work by creating separate directories linked to the same repository. This avoids context leaking and simplifies reviews compared to working directly in the main branch.

How do I set up a Git worktree with language-specific project configurations?

After creating the Git worktree, this skill automatically runs language- or project-specific setup commands and validates a clean baseline before signaling readiness, ensuring dependencies and configurations are correctly installed.

Does creating a Git worktree respect existing project preferences and ignore rules?

Git worktree creation respects project-local or global preferences like CLAUDE.md guidance. The skill verifies ignore rules and prompts the user when no preference is found, ensuring safety checks pass before proceeding.

Why should I use Git worktrees instead of stashing changes for new feature work?

Git worktrees isolate feature work entirely from the main workspace, preventing state contamination and context leaking. Stashing changes risks conflicts and lost context, whereas worktrees maintain a clean baseline for parallel development streams.

Can I use Git worktrees to avoid context switching when starting isolated feature work?

Yes, Git worktrees enable parallel work without switching branches. This skill detects the project name, verifies safety checks, creates the worktree, and runs setup to ensure a clean starting point for your isolated feature work.