tidy-codebase

Codebase cruft removal targets stale files, outdated documentation, and stray build artifacts by scanning for documentation drift and empty directories, delivering a prioritized plan for safe removal and updates across diverse repositories.

The best way to clean up stray build artifacts is to detect outputs not ignored by VCS and surface git hygiene issues like orphaned branches, generating a clear removal plan that restores repository clarity and reduces maintenance noise.

Fixing documentation drift in large repositories involves flagging WIP or outdated docs and aligning them with current features, providing a multi-category analysis that highlights missing docs and suggests necessary updates to reduce confusion.

You can scan for empty directories and orphaned git worktrees across diverse repos by applying multi-category analysis with guardrails, safely surfacing drift between local and remote environments to produce a prioritized cleanup plan.

Yes, the codebase cleanup process includes guardrails to prevent accidental file removal by generating a clear, prioritized removal and update plan, ensuring safe execution across diverse repositories without deleting necessary files.