How do I install the Aico Worktree skill?

Run npx skillmds add majiayu000/aico-worktree in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aico Worktree safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aico Worktree?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aico Worktree free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aico Worktree?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aico Worktree by majiayu000 — Agent Skill

Name: Aico Worktree
Rating: 4.2 (5 reviews)
Author: majiayu000

Aico Worktree

Create isolated git worktree for feature development. Handles directory selection, gitignore verification, project setup, and baseline test verification. Use this skill when: - Starting feature work that needs isolation from current workspace - Before executing implementation plans on a new branch - Want to work on multiple branches/features simultaneously - User asks to "create worktree", "isolate this work", "separate branch" - Need clean baseline before starting major changes Safety: ALWAYS verify worktree directory is gitignored before creating. Process: Check directory → Verify ignored → Create worktree → Run setup → Verify baseline tests

majiayu000 6bddc51 2 files · 3.3 KB Updated Sep 9, 2026 567 repo stars

File contents

Git Worktree

Process

Check existing directories: .worktrees/ or worktrees/
Verify gitignored: MUST verify before creating
Create worktree: git worktree add <path> -b <branch>
Run project setup: Auto-detect (npm/pip/go/cargo)
Verify baseline tests: Run tests, report status

Directory Selection

Priority	Check
1	Existing `.worktrees/`
2	Existing `worktrees/`
3	Project config/docs
4	Ask user

Safety Verification

For project-local directories:

git check-ignore -q .worktrees 2>/dev/null

If NOT ignored → Add to .gitignore first.

Creation Steps

# Create worktree with new branch
git worktree add ".worktrees/$BRANCH_NAME" -b "$BRANCH_NAME"
cd ".worktrees/$BRANCH_NAME"

# Run project setup (auto-detect)
if [ -f package.json ]; then npm install; fi
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi

# Verify baseline tests
npm test / pytest / go test ./...

Report Format

Worktree ready at <full-path>
Branch: <branch-name>
Tests: <N> passing
Ready to implement <feature-name>

Worktree Management

git worktree list          # List all
git worktree remove <path> # Remove after merge
git worktree prune         # Clean stale

Key Rules

ALWAYS verify directory is gitignored for project-local
MUST run baseline tests before reporting ready
If tests fail → Report failures, ask whether to proceed
ALWAYS auto-detect and run project setup

Common Mistakes

❌ Skip ignore verification → ✅ Always verify gitignored
❌ Skip baseline tests → ✅ Verify clean starting point
❌ Proceed with failing tests → ✅ Ask user first
❌ Leave stale worktrees → ✅ Remove after merge

---name: aico-worktreedescription: Create isolated git worktree for feature development. Handles directory selection, gitignore verification, project setup, and baseline test verification. Use this skill when: - Starting feature work that needs isolation from current workspace - Before executing implementation plans on a new branch - Want to work on multiple branches/features simultaneously - User asks to "create worktree", "isolate this work", "separate branch" - Need clean baseline before starting major changes Safety: ALWAYS verify worktree directory is gitignored before creating. Process: Check directory → Verify ignored → Create worktree → Run setup → Verify baseline tests--- # Git Worktree ## Process 1. **Check existing directories**: `.worktrees/` or `worktrees/` 2. **Verify gitignored**: MUST verify before creating 3. **Create worktree**: `git worktree add <path> -b <branch>` 4. **Run project setup**: Auto-detect (npm/pip/go/cargo) 5. **Verify baseline tests**: Run tests, report status ## Directory Selection | Priority | Check | | -------- | ---------------------- | | 1 | Existing `.worktrees/` | | 2 | Existing `worktrees/` | | 3 | Project config/docs | | 4 | Ask user | ## Safety Verification **For project-local directories:** ```bash git check-ignore -q .worktrees 2>/dev/null ``` If NOT ignored → Add to `.gitignore` first. ## Creation Steps ```bash # Create worktree with new branch git worktree add ".worktrees/$BRANCH_NAME" -b "$BRANCH_NAME" cd ".worktrees/$BRANCH_NAME" # Run project setup (auto-detect) if [ -f package.json ]; then npm install; fi if [ -f requirements.txt ]; then pip install -r requirements.txt; fi # Verify baseline tests npm test / pytest / go test ./... ``` ## Report Format ``` Worktree ready at <full-path> Branch: <branch-name> Tests: <N> passing Ready to implement <feature-name> ``` ## Worktree Management ```bash git worktree list # List all git worktree remove <path> # Remove after merge git worktree prune # Clean stale ``` ## Key Rules - ALWAYS verify directory is gitignored for project-local - MUST run baseline tests before reporting ready - If tests fail → Report failures, ask whether to proceed - ALWAYS auto-detect and run project setup ## Common Mistakes - ❌ Skip ignore verification → ✅ Always verify gitignored - ❌ Skip baseline tests → ✅ Verify clean starting point - ❌ Proceed with failing tests → ✅ Ask user first - ❌ Leave stale worktrees → ✅ Remove after merge

Frequently asked questions