worktree-list

List Git worktrees and correlate them with SQLite development track data.

17|8|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/michael-harris/devteam --skill worktree-list-michael-harris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-list
Source: https://github.com/michael-harris/devteam/tree/main/skills/worktree-list
Command: npx skills add https://github.com/michael-harris/devteam --skill worktree-list-michael-harris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers diagnose and understand the status of their Git worktrees, especially in complex multi-track development environments.

Core Features & Use Cases

  • Comprehensive Listing: Displays all native Git worktrees and legacy DevTeam worktrees.
  • State Correlation: Links Git worktrees to development track information stored in the SQLite database.
  • Use Case: When encountering unexpected Git behavior or needing to audit the project's branching strategy, this command provides a clear overview of all active work areas.

Quick Start

Run the command to list all git worktrees and their associated development track information.

Frequently Asked Questions about worktree-list

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all git worktrees in a multi-track development environment?

To list git worktrees across multi-track environments, run a diagnostic command that retrieves all native Git worktrees and legacy DevTeam worktrees, correlating them with development track information from the SQLite state database for a comprehensive overview.

What is a git worktree and when do I need to track it?

A git worktree is a linked working directory attached to your main repository. You need to track worktrees when managing complex multi-track development environments to audit branching strategies and diagnose unexpected Git behavior across active work areas.

How do I correlate git worktrees with development track data in a SQLite database?

Correlating git worktrees with development track data involves linking Git worktree command outputs to state records retrieved from the SQLite database, providing a diagnostic overview mapping each active work area to its corresponding track.

Does listing git worktrees require access to a SQLite state database?

Listing git worktrees with state correlation requires access to Git commands, shell utilities, and the SQLite database for state retrieval, ensuring the diagnostic overview accurately links worktrees to their development track information.

Why does my git branching strategy need auditing with worktree tracking?

Auditing your git branching strategy with worktree tracking is necessary when encountering unexpected Git behavior or managing multiple parallel tracks, as it provides a clear overview of all active work areas and their associated development states.