cleanup-manager

Stale branch cleanup identifies merged or inactive branches and deletes them with safety checks for protected branches and dry-run mode. Use dry-run first to preview deletions, then confirm with explicit approval before removing branches locally or remotely.

Yes, cleanup-manager deletes stale branches across both local and remote locations in a single operation. Configure protection rules for branches you want to keep, then apply deletions uniformly across your repository with optional force mode.

Use dry-run mode to list inactive branches without deletion, review the candidates, then execute with explicit confirmation. Protected-branch filters prevent accidental removal of critical branches, and structured reports show all deletion actions for audit trail.

Configure protected-branch rules in your setup to exclude branches you want to preserve. The Skill enforces these constraints before deletion, ensuring that main, develop, or release branches remain untouched regardless of their merge or activity status.

Yes, cleanup-manager identifies both merged branches—already integrated into main—and inactive branches based on age. Apply merge and inactivity rules independently to target the exact stale-branch types your workflow needs to remove.

Cleanup-manager uses platform-specific handler delegation to support different Git systems. Core logic applies merged and inactivity filters universally, with platform handlers managing the actual deletion operations across your environment.