worktree-status

Audit git worktrees and report dirty and merge status.

11.1k|1.3k|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/MoonshotAI/kimi-cli --skill worktree-status-moonshotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-status
Source: https://github.com/MoonshotAI/kimi-cli/tree/main/.agents/skills/worktree-status
Command: npx skills add https://github.com/MoonshotAI/kimi-cli --skill worktree-status-moonshotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit all git worktrees in the current project and determine their dirty and merge status to guide safe cleanup.

Core Features & Use Cases

  • List all worktrees and show each one's branch, dirty state, and merge status.
  • Detect whether a branch is squash-merged via content diffs and identify safe cleanup candidates.
  • Optional checks for related tmux sessions and present results in a structured Markdown table.

Quick Start

Run a status report for all worktrees in the current project.

Frequently Asked Questions about worktree-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 project?

To check git worktree status, you can run an audit that enumerates all worktrees in the current project, reporting each branch's dirty state and merge status in a structured Markdown table.

How can I tell if a squash-merged branch is safe to clean up?

To identify safe cleanup candidates for a squash-merged branch, the audit verifies merge status through content diffs, detecting whether the branch changes are already integrated into the target.

What is the best way to identify dirty git worktrees before batch cleanup?

The best way to identify dirty git worktrees before batch cleanup is to run a status report that determines the dirty state of each worktree, ensuring uncommitted changes are validated before deletion.

Does the worktree audit check for active tmux sessions?

Yes, the worktree audit includes optional checks for related tmux sessions, presenting the overall dirty and merge status alongside session data in a structured Markdown table.

Can I use this to verify branch merge status across multiple worktrees?

Yes, you can verify branch merge status across multiple worktrees by running the audit, which relies on Git tooling to enumerate worktrees and check merge status through content diffs.