housekeep

To prune stale worktrees and clean up local git repositories, you can automate maintenance tasks that remove dirt files, sync with main, and verify repo health safely. This process uses idempotent phases with dry-run support and guardrails to prevent deleting tracked files.

Automating branch hygiene across multiple worktrees involves running a centralized maintenance process that prunes merged branches, removes dirt files, and syncs operations with the main branch. This keeps the codebase healthy and reduces workflow drift without affecting tracked data.

Yes, you can safely remove dirt files from your codebase without deleting tracked git data by using maintenance scripts equipped with guardrails. These automated phases are idempotent and feature dry-run support to ensure only untracked clutter is removed.

You generate a local health report for your git repository by running an automated maintenance routine that verifies repo health, syncs with main, and prunes merged branches. The resulting report highlights stale worktrees and overall codebase status.

Automated repo cleanup works effectively with multiple local worktrees by applying idempotent housekeeping phases across the entire codebase. It prunes stale worktrees and cleans dirt files while maintaining strict guardrails to prevent accidental deletion of active worktrees or tracked files.