worktree-status

Identify the active git worktree and check its cleanliness.

13|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/phenobarbital/antigravity-config --skill worktree-status-phenobarbital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-status
Source: https://github.com/phenobarbital/antigravity-config/tree/main/backend/.agent/skills/worktree-status
Command: npx skills add https://github.com/phenobarbital/antigravity-config --skill worktree-status-phenobarbital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show the current git worktree setup, identify the active or likely-active worktree, and remind you to work only inside the correct directory to prevent accidental edits.

Core Features & Use Cases

  • List all git worktrees with git worktree list and identify the primary and any additional worktrees.
  • Detect the active or likely-active worktree using recorded data or heuristics, and report its path and branch.
  • Check repository cleanliness with git status to confirm there are no unintended changes and remind about guardrails.
  • Provide a clear reminder to perform feature work inside the active worktree, or suggest creating one if none exists.

Quick Start

Use the worktree-status skill to verify the current git worktree setup and confirm you are operating inside the correct worktree.

Frequently Asked Questions about worktree-status

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

FAQPage Schema
How do I check my git worktree status to prevent accidental edits?

Check your git worktree status by listing all worktrees and analyzing the active directory's cleanliness. This identifies the likely-active worktree and reports its path and branch to ensure you only edit files in the correct working location.

How do I verify which git worktree is currently active?

Verify the active git worktree using recorded data and heuristics applied to the worktree list. This detects the likely-active worktree, confirms its current branch, and provides a clear reminder to perform feature work inside that specific directory.

Why does git status show changes when I am in the wrong worktree?

Git status shows unexpected changes because you are likely operating outside the active worktree. Running a worktree sanity-check identifies the correct working directory and confirms repository cleanliness, preventing unintended modifications in non-active branches.

What is the best way to manage multiple git worktrees during daily development?

The best way to manage multiple git worktrees is to run a status check that lists all directories, detects the active branch, and enforces guardrails. This prevents accidental cross-directory edits and maintains repository cleanliness across your workflow.

Do I need an existing git repository to use worktree status checks?

Yes, you need an existing git repository with worktrees configured. The status check runs git worktree list and git status commands to identify your active working directory, meaning a initialized repository structure is required for the sanity-check.

Can I create a new git worktree if the status check finds none?

If the status check finds no active worktree, it suggests creating one to maintain proper guardrails. This ensures you have a designated working directory for feature work and prevents untracked changes in your primary repository branch.