cleanup

To clean up stale git branches and orphaned worktrees, you can scan your repository for merged, outdated, or untracked branches and worktrees, then approve prune and delete operations to reduce clutter. The process generates an auditable report before removing anything.

The safest way to remove local git branches involves separating deletions into safe categories like merged branches, and those requiring confirmation like unmerged branches. Guardrails prevent deleting the current branch or main and master, ensuring protected refs remain intact.

GitHub PR status helps determine if a branch is stale by checking whether associated pull requests are closed or merged versus still active. This prevents removing branches that are actively reviewed or pending merge, adding an extra layer of safety to the cleanup process.

Yes, you need both git and gh installed to prune stale branches and worktrees using this approach. The git dependency handles local state-gathering and worktree management, while gh queries GitHub for pull request states to verify branch staleness accurately.

Orphaned git worktrees left behind after deletions or ref moves are identified during the repository scan and included in the cleanup report. You can then approve their removal to prevent outdated refs from accumulating and wasting build time.

Yes, you can review what will be deleted before executing cleanup because the tool produces an auditable report separating safe removals from risky ones. You approve only the specific items you want removed, ensuring no unexpected deletions occur.