worktree-status

To check git worktree status before cleanup, pull the latest main branch and inspect each worktree to report its dirty state and merge status in a Markdown table. This identifies which worktrees are safe for batch removal.

Auditing git worktree branches and dirty state involves pulling the latest main branch and inspecting each worktree to report its branch, dirty state, and merge status in a Markdown table for effective management.

To find merged git worktrees safe to delete, pull the latest main branch and inspect each worktree's merge status and dirty state to identify which ones can be safely cleaned up before batch operations.

You can use a bash script to report git worktree merge status in a Markdown table by pulling the latest main branch and inspecting each worktree to output its branch, dirty state, and merge status.

Yes, you need to pull the main branch before checking worktree cleanliness because the audit procedure enforces a mandatory pull of the latest main to accurately verify each worktree's merge status and dirty state.

You should audit worktree status before batch cleanup operations to identify dirty state and merge status, ensuring you only remove worktrees that are clean and fully merged, preventing accidental data loss.