How do I install the Worktree Execution skill?

Run npx skillmds@latest add shinpr/worktree-execution 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 Worktree Execution safe to use?

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

Which AI agents work with Worktree Execution?

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 Worktree Execution free to use?

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

Who published Worktree Execution?

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

Worktree Execution by shinpr — Agent Skill

Name: Worktree Execution
Author: shinpr

File contents

Worktree Execution Skill

Architecture

Two isolated worktrees enable parallel prompt execution.

Orchestrator
    │
    ├── Create Worktrees (in ${TMPDIR:-/tmp}/)
    │       ├── worktree-rashomon-original-{timestamp}
    │       └── worktree-rashomon-optimized-{timestamp}
    │
    ├── Parallel Execution (Agent tool)
    │       ├── Execution 1 → worktree-rashomon-original
    │       └── Execution 2 → worktree-rashomon-optimized
    │
    ├── Collect Results (await both)
    │
    └── Cleanup Worktrees (always)

Worktree Management

Creation

Script: scripts/worktree-create.sh

# Default labels (original/optimized) for prompt eval
./scripts/worktree-create.sh [repo_root]

# Custom labels for skill eval
./scripts/worktree-create.sh [repo_root] baseline with-skill
./scripts/worktree-create.sh [repo_root] old-version new-version

# Pin every pair in an evaluation run to the same commit
./scripts/worktree-create.sh [repo_root] trial-a trial-b [base_sha]

Output (stdout):

/tmp/worktree-rashomon-{label_a}-20260114-123456
/tmp/worktree-rashomon-{label_b}-20260114-123456

Properties:

Location: ${TMPDIR:-/tmp}/
Naming: worktree-rashomon-{label}-{timestamp}
Branch: Detached HEAD at the pinned base commit
Base commit: Caller-supplied SHA, resolved once per evaluation
Active marker: Git worktree lock containing run ID, owner PID, start time, and lease expiry
Labels default to original / optimized if not specified

Cleanup

Script: scripts/worktree-cleanup.sh

# Remove all rashomon worktrees
./scripts/worktree-cleanup.sh [repo_root]

# Remove specific worktrees
./scripts/worktree-cleanup.sh [repo_root] path1 path2

# Remove registered orphaned worktrees, including expired Rashomon locks
./scripts/worktree-cleanup.sh --orphans [repo_root]

Cleanup Triggers:

After successful report generation
In finally block on any failure
On timeout
On startup (orphan detection)

Parallel Execution Principle

Key: To achieve true parallel execution, send both Agent invocations in a single message.

The calling command determines which agents to invoke and how to structure the Agent invocations. This skill provides only the worktree infrastructure.

Error Handling (Worktree Operations)

Scenario	Behavior
Creation fails	Report git error, suggest checking repository state
Cleanup fails	Log warning, attempt orphan cleanup on next run
Unlocked orphan	Remove registered Rashomon worktree after 1 hour
Crashed locked run	Remove after owner disappearance plus orphan age, or after lease expiry
Active long run	Set `RASHOMON_LEASE_SECONDS` before creation so the lease covers the run

Scripts Reference

worktree-create.sh

Exit Code	Meaning
0	Success
1	Not a git repository
2	Creation failed

worktree-cleanup.sh

Exit Code	Meaning
0	Success (or nothing to clean)
1	Not a git repository
2	Cleanup partially failed

Constraints

No concurrent comparisons: One rashomon execution per repository
Git required: A version supporting git worktree lock
Disk space: Sufficient space for worktree copies

---name: worktree-executiondescription: Creates, pins, and cleans isolated Git worktree pairs for comparison trials. Use only when a Rashomon prompt or skill evaluation needs paired execution environments or orphan recovery.---# Worktree Execution Skill## ArchitectureTwo isolated worktrees enable parallel prompt execution.```Orchestrator │ ├── Create Worktrees (in ${TMPDIR:-/tmp}/) │ ├── worktree-rashomon-original-{timestamp} │ └── worktree-rashomon-optimized-{timestamp} │ ├── Parallel Execution (Agent tool) │ ├── Execution 1 → worktree-rashomon-original │ └── Execution 2 → worktree-rashomon-optimized │ ├── Collect Results (await both) │ └── Cleanup Worktrees (always)```## Worktree Management### Creation**Script**: `scripts/worktree-create.sh````bash# Default labels (original/optimized) for prompt eval./scripts/worktree-create.sh [repo_root]# Custom labels for skill eval./scripts/worktree-create.sh [repo_root] baseline with-skill./scripts/worktree-create.sh [repo_root] old-version new-version# Pin every pair in an evaluation run to the same commit./scripts/worktree-create.sh [repo_root] trial-a trial-b [base_sha]```**Output** (stdout):```/tmp/worktree-rashomon-{label_a}-20260114-123456/tmp/worktree-rashomon-{label_b}-20260114-123456```**Properties**:- Location: `${TMPDIR:-/tmp}/`- Naming: `worktree-rashomon-{label}-{timestamp}`- Branch: Detached HEAD at the pinned base commit- Base commit: Caller-supplied SHA, resolved once per evaluation- Active marker: Git worktree lock containing run ID, owner PID, start time, and lease expiry- Labels default to `original` / `optimized` if not specified### Cleanup**Script**: `scripts/worktree-cleanup.sh````bash# Remove all rashomon worktrees./scripts/worktree-cleanup.sh [repo_root]# Remove specific worktrees./scripts/worktree-cleanup.sh [repo_root] path1 path2# Remove registered orphaned worktrees, including expired Rashomon locks./scripts/worktree-cleanup.sh --orphans [repo_root]```**Cleanup Triggers**:- After successful report generation- In finally block on any failure- On timeout- On startup (orphan detection)## Parallel Execution Principle**Key**: To achieve true parallel execution, send both Agent invocations in a single message.The calling command determines which agents to invoke and how to structure the Agent invocations. This skill provides only the worktree infrastructure.## Error Handling (Worktree Operations)| Scenario | Behavior ||----------|----------|| Creation fails | Report git error, suggest checking repository state || Cleanup fails | Log warning, attempt orphan cleanup on next run || Unlocked orphan | Remove registered Rashomon worktree after 1 hour || Crashed locked run | Remove after owner disappearance plus orphan age, or after lease expiry || Active long run | Set `RASHOMON_LEASE_SECONDS` before creation so the lease covers the run |## Scripts Reference### worktree-create.sh| Exit Code | Meaning ||-----------|---------|| 0 | Success || 1 | Not a git repository || 2 | Creation failed |### worktree-cleanup.sh| Exit Code | Meaning ||-----------|---------|| 0 | Success (or nothing to clean) || 1 | Not a git repository || 2 | Cleanup partially failed |## Constraints- **No concurrent comparisons**: One rashomon execution per repository- **Git required**: A version supporting `git worktree lock`- **Disk space**: Sufficient space for worktree copies

Frequently asked questions

Worktree Execution