cleanup

Automating git worktree cleanup removes stale development branches and worktrees after merging by targeting specific story or epic IDs to safely transition states and delete remote branches. You can execute bulk operations or target individual items.

Archiving completed stories and closing epics is best handled by targeting specific IDs like story-NNN or epic-NNN, which marks them done, prunes associated worktrees, and removes merged branches to maintain repository hygiene and reduce drift.

Yes, you can run a dry-run status to preview the cleanup workflow. This allows you to verify which stale worktrees, stories, and epics will be targeted before any actual state transitions or remote branch deletions occur.

Cleaning up in-progress worktrees triggers prompts for items containing uncommitted changes, ensuring safe state transitions. This prevents accidental data loss during the pruning of stale worktrees, branches, and completed stories.

Yes, the cleanup automation supports bulk operations by using the 'all' token, executing the full workflow to archive stories, close epics, and prune every stale worktree and merged branch across the repository in one action.