gitwhat

Concise git workspace snapshot for the current directory. Use when asked to show current branch, cwd, repo root, whether the current directory is a worktree, local dirty status, or whether other worktrees have uncommitted changes.

⭐2stars🔀1forks📁View on GitHub🕐Updated Dec 31, 2025

When & Why to Use This Skill

Gitwhat is a high-efficiency Claude skill designed to provide a concise, real-time snapshot of your Git workspace. It streamlines repository management by instantly reporting the current branch, repository root, and local dirty status, while uniquely tracking uncommitted changes across multiple Git worktrees without requiring network access. This tool is essential for developers who need to maintain context and state awareness in complex multi-repo or multi-worktree environments.

Use Cases

  • Case 1: Quickly verify the current working directory and active Git branch before executing deployment or merge commands.
  • Case 2: Monitor the 'dirty' status of local repositories to ensure all changes are committed or stashed before switching tasks.
  • Case 3: Manage complex development environments by tracking uncommitted changes across multiple Git worktrees simultaneously to prevent data loss.
  • Case 4: Identify the repository root and worktree structure when navigating deep directory hierarchies in large-scale projects.
namegitwhat
descriptionConcise git workspace snapshot for the current directory. Use when asked to show current branch, cwd, repo root, whether the current directory is a worktree, local dirty status, or whether other worktrees have uncommitted changes.

Gitwhat

Overview

Provide a short, formatted git status snapshot for the current working directory and any sibling worktrees.

Quick start

  • Run scripts/gitwhat.sh from the target directory.
  • If not inside a git repo, report the cwd and exit.

Output fields

  • CWD
  • Branch (or detached@)
  • Repo root
  • Worktree (yes/no + name or main)
  • Status (clean/dirty with counts)
  • Other worktrees (clean/dirty per worktree)

Notes

  • Keep output compact and use the script output as-is unless the user asks for more detail.
  • Do not use network calls; rely on local git commands.