wt-status

Report git worktree status and branch sync across all worktrees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers working with multiple git worktrees often struggle to see the current state, uncommitted changes, and how branches are syncing across all worktrees. This skill provides a centralized view to reduce context switching.

Core Features & Use Cases

  • Current worktree overview: Show the status of the active worktree.
  • All worktrees: List every worktree and its state, including uncommitted changes.
  • Sync awareness: Highlight ahead/behind status relative to origin to understand what needs pushing or pulling.
  • Use Case: When coordinating work across several feature branches, quickly verify what’s modified and what’s out of date.

Quick Start

Run the /wt:status slash command to display the status across all worktrees.

Frequently Asked Questions about wt-status

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

FAQPage Schema
How do I check uncommitted changes across multiple git worktrees?

To check uncommitted changes across multiple git worktrees, you need a centralized status view that queries git worktree data and presents a comprehensive snapshot of modifications. This reduces context switching by showing the state of every worktree in one report.

What is the best way to get a full snapshot of all git worktrees?

The best way to get a full snapshot of all git worktrees is to query worktree data to display current status, uncommitted changes, and branch sync information. This provides a centralized view to reduce context switching when managing several feature branches.

Can I see if my git worktree branches are ahead or behind origin?

Yes, you can see if git worktree branches are ahead or behind origin by highlighting sync awareness status. This allows you to understand what needs pushing or pulling to keep branches up to date across the entire worktree set.

How do I track uncommitted changes when coordinating work across several feature branches?

To track uncommitted changes when coordinating work across several feature branches, run a slash command to display the status across all worktrees. This quickly verifies what is modified and out of date without manual context switching.

Does this worktree status overview require any special dependencies?

No, this worktree status overview requires no special dependencies to function. It directly queries your local git worktree data to present the current state, uncommitted changes, and branch sync information.

When do I need a centralized git worktree status view?

You need a centralized git worktree status view when managing multiple worktrees and struggling to see the current state. It is applicable for developers who need to quickly identify uncommitted changes and track branch sync across the set.