What is a development track?

A development track is a named workspace linked to a worktree, tracked in the .devteam/devteam.db state database.

How does this help debugging?

It correlates git worktrees with their tracks and shows HEAD, branch, status, and size to spot discrepancies.

What if there are no worktrees?

The tool reports no development track worktrees and indicates if state-only mode is active or if you’re not in a git repository.

worktree-list

npx machina-cli add skill michael-harris/devteam/worktree-list --openclaw

Files (1)

SKILL.md

3.5 KB

Git worktrees: !git worktree list 2>/dev/null || echo "Not a git repository" Native worktrees: !ls -d .claude/worktrees/*/ 2>/dev/null || echo "None" Legacy worktrees: !ls -d .multi-agent/track-*/ 2>/dev/null || echo "None" State DB exists: !test -f .devteam/devteam.db && echo "yes" || echo "no"

Worktree List Command

Debug/Expert Command - List all git worktrees with development track information.

Note: This command is rarely needed. Worktrees are managed automatically by /devteam:implement. Use this only for debugging worktree issues.

Command Usage

/devteam:worktree list           # List all worktrees

Your Process

Step 1: Get Git Worktrees

# Get all git worktrees
git worktree list --porcelain

Step 2: Load State from SQLite

Query the SQLite database (.devteam/devteam.db) to correlate git worktrees with development tracks:

source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
# Track info available via get_state "parallel_tracks.track_info.*"

Step 3: Display Worktree Information

Git Worktrees

Mode: Git worktrees enabled
State database: .devteam/devteam.db

Main Repository:
Path: /home/user/my-project
Branch: main
HEAD: abc123 (2 hours ago)

Development Track Worktrees:

Track 01: Backend API
  Path: /home/user/my-project/.multi-agent/track-01
  Branch: dev-track-01
  HEAD: def456 (30 min ago)
  Status: Complete (2/2 sprints)
  Size: 45 MB

Track 02: Frontend
  Path: /home/user/my-project/.multi-agent/track-02
  Branch: dev-track-02
  HEAD: ghi789 (1 hour ago)
  Status: In Progress (1/2 sprints)
  Size: 52 MB

Track 03: Infrastructure
  Path: /home/user/my-project/.multi-agent/track-03
  Branch: dev-track-03
  HEAD: jkl012 (2 hours ago)
  Status: Pending (0/2 sprints)
  Size: 38 MB

Summary
Total worktrees: 4 (1 main + 3 tracks)
Total disk usage: ~135 MB
Tracks complete: 1/3

Commands:
  Status: /devteam:worktree status
  Cleanup: /devteam:worktree cleanup
  Merge: /devteam:merge-tracks

Alternative: Simple Format

Worktrees:
  main       /home/user/my-project                             (abc123)
  track-01   /home/user/my-project/.multi-agent/track-01       (def456) complete
  track-02   /home/user/my-project/.multi-agent/track-02       (ghi789) active
  track-03   /home/user/my-project/.multi-agent/track-03       (jkl012) pending

Error Handling

No worktrees:

No development track worktrees found.

This project is using state-only mode (not git worktrees).

To use worktrees:
  /devteam:plan (worktrees are auto-configured for multi-track plans)

Git command fails:

Error: Could not list git worktrees

Make sure you're in a git repository:
  git status

If git is not working, check git installation:
  git --version

Worktree Sources

Display worktrees from both sources:

Native Claude Code worktrees: .claude/worktrees/ (from isolation: worktree)
Legacy DevTeam worktrees: .multi-agent/track-*/ (from manual management)

Notes

Shows all worktrees (not just multi-agent tracks)
Correlates with SQLite state database for track information
Displays disk usage per worktree
Quick reference for expert users

Overview

This skill lists all git worktrees in a project and links them to development tracks, including native Claude code worktrees and legacy DevTeam tracks, by correlating with a SQLite state database. It serves as a debugging aid for multi-track development setups and diagnostics.

How This Skill Works

It enumerates worktrees using git worktree list --porcelain, then loads track state from the SQLite database at .devteam/devteam.db via a helper script, exposing track information. The output highlights a Main Repository and Development Track Worktrees with path, branch, HEAD, status, and size, pulling track data from the state store for accuracy.

When to Use It

When managing a project that uses native Claude code worktrees and legacy DevTeam tracks.
When debugging discrepancies between listed worktrees and their development tracks.
When verifying disk usage per worktree and total usage.
When correlating git worktrees with track information from the state database.
When diagnosing a Git worktree command failure or missing worktrees.

Quick Start

Step 1: Get Git Worktrees - git worktree list --porcelain
Step 2: Load State from SQLite - source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
Step 3: Display Worktree Information - review the output showing Main Repository and Track worktrees

Best Practices

Run in a git repository to ensure git worktree list works reliably.
Use porcelain output (--porcelain) for stable parsing in scripts.
Load and verify the SQLite state at .devteam/devteam.db to correlate tracks.
Consider both Native Claude worktrees (.claude/worktrees) and Legacy tracks (.multi-agent/track-*/).
Choose the simple format for quick reports or the detailed display for in-depth debugging.

Example Use Cases

A project with a main repository and three development tracks under .multi-agent/track-01 to track features.
A Claude-based project using .claude/worktrees alongside legacy tracks for extended testing.
Debugging a mismatch where a track shows complete but the worktree HEAD differs from the main repo HEAD.
Verifying per-track disk usage (e.g., Track-01: 45 MB, Track-02: 52 MB, Track-03: 38 MB).
Diagnosing a Git command failure by confirming repo state and the presence of worktrees.

Frequently Asked Questions

Add this skill to your agents