Create isolated git worktrees in ~/.claude-worktrees/. Use when user says "create an isolated copy", "worktree", "create worktree", "isolated workspace", or needs to work on a branch without affecting the main working directory.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: git-worktree description: Create isolated git worktrees in ~/.claude-worktrees/. Use when user says "create an isolated copy", "worktree", "create worktree", "isolated workspace", or needs to work on a branch without affecting the main working directory. allowed-tools: Bash, Read
Git Worktree
Create isolated git worktrees in ~/.claude-worktrees/<repo>/<branch>/.
Supports .worktreeinclude file for copying untracked files (e.g., .env.local) to new worktrees.
Usage
Create Worktree
BRANCH_NAME="feature/my-feature" ./scripts/create-worktree.sh
# Or with ticket URL for branch naming:
BRANCH_NAME="eng-123/fix-bug" TICKET_URL="https://linear.app/team/issue/ENG-123/fix-bug" ./scripts/create-worktree.sh
# Or with custom base branch:
BRANCH_NAME="feature/my-feature" BASE_BRANCH="develop" ./scripts/create-worktree.sh
Outputs (to stdout):
BRANCH_NAME=<branch>- The created branch nameWORKTREE_PATH=<path>- Absolute path to worktreeDEFAULT_BRANCH=<branch>- Repository's default branch
Remove Worktree
WORKTREE_PATH="$HOME/.claude-worktrees/my-repo/my-branch" ./scripts/remove-worktree.sh
.worktreeinclude
Create a .worktreeinclude file in your repo root to specify files that should be copied to new worktrees:
# Environment files
.env.local
.env.development
# Local config
config/local.json
Supports glob patterns via bash globbing (**/*.local).
Scripts
create-worktree.sh- Create worktree, copy includescopy-worktree-includes.sh- Copy files from .worktreeincluderemove-worktree.sh- Remove worktree and clean up
More by kvnxiao
View allGenerate external API documentation in HTML format for Squint APIs. Use when asked to document an API endpoint, create API docs for external consumers, or generate HTML documentation for endpoints. Output is Google Docs compatible.
Review and improve repository documentation including both human-readable docs (`docs/`), `README.md`, and AI agent memory context files (`CLAUDE.md`, `CODEX.md`, `AGENTS.md`, `.cursorrules`, etc.) for clarity, minimal duplication, and modularity. Use when asked to review, audit, refactor, or improve documentation structure, consolidate rules, reduce redundancy, establish shared standards, or modularize monolithic instruction files.
