worktree-janitor

Run the janitor script to perform a safe prune of git worktrees by auditing merged local branches and stale metadata. Confirm the audit results before executing guarded removal commands that protect your current worktree from deletion.

Use a deterministic, script-based workflow to audit git worktrees across multiple repositories, identifying merged or unused entries and stale metadata. This provides clear safety checks to review eligibility before any cleanup actions are taken.

Yes, you can safely clean stale git worktree metadata without affecting current work by using a guarded prune workflow. Built-in safety guardrails protect the active worktree while removing only stale entries and fully merged local branches.

Run an audit command to identify merged local branches eligible for git worktree cleanup by checking branch metadata and flagging fully merged branches as safe for removal. This prevents accidental deletion of branches with work in progress.

Before removing unused git worktrees, run an audit to review all entries and verify which worktrees are stale or merged. Always confirm the audit results to ensure no active work is lost before executing the prune workflow.

You should not use a script to clean up git worktrees when you have uncommitted changes in an unused worktree, as automated audits may not detect them. Always manually verify work in progress before running any prune or remove commands.