worktree-status

List active git worktrees with branch and change status.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ttsmith21/swcsharpaddin --skill worktree-status-ttsmith21
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-status
Source: https://github.com/ttsmith21/swcsharpaddin/tree/main/.claude/skills/worktree-status
Command: npx skills add https://github.com/ttsmith21/swcsharpaddin --skill worktree-status-ttsmith21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify all active git worktrees and report their status to simplify multi-worktree management.

Core Features & Use Cases

  • List all active worktrees with their branch and change status.
  • Detect uncommitted changes in each worktree and highlight potential issues.
  • Provide quick navigation instructions to inspect or modify any worktree.

Quick Start

List all git worktrees and display each path, branch, and change status.

Frequently Asked Questions about worktree-status

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

FAQPage Schema
How do I show all git worktrees and their uncommitted change status?

To show git worktrees and their status, the skill reads 'git worktree list' outputs and inspects each worktree path for uncommitted changes via 'git -C <path> status --short'. It reports each worktree's branch, cleanliness, and flags stale paths.

What is the best way to check multiple git worktrees for uncommitted changes?

The best way to check multiple git worktrees for uncommitted changes is to run a status scan across all active paths. The skill identifies all active worktrees and highlights any uncommitted changes or inaccessible paths detected during the inspection.

How do I list active git worktrees and detect stale paths?

To list active git worktrees and detect stale paths, the skill parses 'git worktree list' and validates each directory. It flags any stale or inaccessible paths while reporting the associated branch and change status for every active worktree.

Can I use this to navigate to a specific git worktree after checking its status?

Yes, you can use this to navigate to a specific git worktree. After identifying all active worktrees and their change status, the skill provides quick navigation instructions so you can inspect or modify any worktree path directly.

Does this work with multi-worktree repository workflows?

Yes, this works with multi-worktree repository workflows. It is specifically applicable to repositories using multiple worktrees, providing quick visibility into each worktree's path, branch, and cleanliness status.

Why does my git worktree status check fail on inaccessible paths?

A git worktree status check fails on inaccessible paths when directories become stale or detached from the main repository. The skill actively flags these stale or inaccessible paths during its worktree inspection process.