worktrees:status

Consolidate Git worktree status across a repository using standard Git commands.

4|1|Updated Jan 23, 2026

Search Tags:#git #worktrees #audit #status #prune #locked

Ready to run

npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktrees:status
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/worktrees/skills/status
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill worktrees-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates visibility into Git worktrees, consolidating information about active worktrees, stale references, uncommitted changes, and locked states to prevent confusion and improve maintenance.

Core Features & Use Cases

Active Worktree Overview: Lists all active worktrees and their current branches.
Stale Reference Detection: Highlights references that need pruning to keep the worktree graph healthy.
Cross-Worktree Change Audit: Detects uncommitted changes across all worktrees for quick cleanup.
Lock State Awareness: Identifies worktrees that are currently locked to prevent conflicts.

Quick Start

Use the worktrees:status skill to scan your repository and produce a compact status report. Steps:

Run: git worktree list
Run: git worktree prune --dry-run
Inspect the output to identify any worktrees with changes and any locked worktrees.

Frequently Asked Questions about worktrees:status

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

FAQPage Schema

How do I check the status of all git worktrees in my repository?▼

You can check git worktree status by running a consolidated scan that lists all active worktrees, their current branches, uncommitted changes, and locked states to provide a complete repository overview.

How do I find stale references and locked worktrees before pruning?▼

To find stale references and locked worktrees, run a dry-run prune command to inspect the worktree graph, highlighting references needing pruning and identifying locked states to prevent conflicts.

Can I detect uncommitted changes across multiple git worktrees at once?▼

Yes, detecting uncommitted changes across multiple git worktrees is possible by running a cross-worktree audit that gathers data from all active worktrees and deterministically reports any pending modifications.

What is the best way to audit active git worktrees and their current branches?▼

To audit active git worktrees and their current branches, use standard git commands to list worktrees, consolidating the data into a single deterministic status report.

Does git worktree status reporting require any external dependencies?▼

Git worktree status reporting requires no external dependencies, as it uses standard built-in git commands to gather worktree data and present results deterministically.