worktree-status

To check git worktree status, audit and report the branch, dirty state, and merge status of all worktrees at once. This generates a Markdown table summarizing which worktrees are safe for cleanup and which branches are merged.

The best way to identify git worktrees for cleanup is to audit their merge status and dirty state. By checking if a branch is merged and the worktree is clean, you can safely determine which worktrees are ready for batch deletion.

To detect squash-merged branches in git worktrees, the audit process performs content diffs against the main branch. It enforces a mandatory pull of the latest main before iterating worktrees to accurately identify squash merge statuses.

Yes, you can audit git worktree merge status before batch cleanup. It guides pre-cleanup decisions by reporting branch dirtiness and merge statuses, reducing the risk of accidentally deleting unmerged or modified worktrees.

Auditing git worktree status requires pulling the main branch to ensure merge statuses are checked against the latest changes. This mandatory pull guarantees accurate content diffs when detecting whether branches are squash-merged.