worktree-status

To check if a git worktree is safe to delete, you need to verify its branch's merge status and whether it contains uncommitted dirty changes. This Skill audits every worktree, pulling the latest main to report merged status and cleanup viability in a Markdown table.

You can find dirty git worktrees by inspecting each one for uncommitted modifications. This Skill audits the repository's worktrees, identifying the current branch and dirty state, then presenting the complete status report in a structured Markdown table.

The best way to audit git worktrees before a release is to pull the latest main and inspect each worktree's merge status. This Skill validates your project structure by generating a Markdown table with branch, dirty state, and cleanup viability.

Yes, you can see which git worktree branches have been merged by pulling the latest main and checking each branch's status. This Skill reports the merged status of all worktrees in the current repository within a Markdown table.

You should audit worktrees before batch-cleaning to avoid data loss from deleting branches with unmerged changes. This Skill enforces pulling the latest main and provides guidance on dirty state and cleanup viability before you remove any worktrees.