aico-worktree_skill

Overview

This skill creates an isolated git worktree for feature development and ensures a clean, reproducible starting point. It handles directory selection, enforces gitignore safety, runs project setup, and verifies baseline tests before reporting readiness. Use it to avoid contaminating your main workspace and to work on multiple branches concurrently.

How this skill works

The skill inspects the repository for preferred worktree locations (.worktrees/ or worktrees/) and falls back to project docs or prompts the user. It verifies the chosen directory is listed in .gitignore before creating a new branched worktree with git worktree add. After creation it auto-detects the project type (npm, pip, go, cargo), runs setup commands, and executes baseline tests, reporting pass/fail results and test counts.

When to use it

• Starting a feature that must be isolated from the current workspace
• Before executing an implementation plan on a new branch
• When working on multiple branches or features at the same time
• User asks to “create worktree”, “isolate this work”, or “separate branch”
• Need a clean baseline before major refactors or experiments

Best practices

• Always verify the worktree directory is gitignored for project-local paths before creating
• Prefer .worktrees/ then worktrees/ when present; consult project docs next
• Auto-run dependency install and environment setup to reproduce developer environment
• Run baseline tests immediately and do not proceed if tests fail without user approval
• Remove or prune stale worktrees after branches are merged to avoid clutter

Example use cases

• Create isolated worktree and branch for a new feature without affecting open editors or uncommitted changes
• Spin up parallel worktrees to implement and test two competing approaches simultaneously
• Prepare a clean environment to reproduce and fix a flaky test or CI failure
• Start a large refactor on a feature branch after confirming baseline tests pass