repo-cleanup

To find obsolete files and dead code in your git repository, run a systematic audit that scans for tracked build artifacts, backups, and zero-reference modules. This generates a read-only, categorized action plan detailing exactly what clutter exists and why it is considered safe to remove.

The best way to fix .gitignore mismatches is to audit tracked files against existing ignore rules, which identifies artifacts that should have been ignored. This process produces an exact .gitignore patch you can apply to prevent future repository bloat from build and test outputs.

Dead code detection works by scanning frontend utilities and backend modules for zero external references across the codebase. It flags potentially unused components and non-standard modules as orphaned, categorizing them in a read-only report for review before any deletion occurs.

Yes, you can audit repository hygiene without risking destructive git operations. The audit follows an approval-first approach that only produces a prioritized, read-only action plan and recommended patches, ensuring no files are actually deleted or modified until you explicitly review and approve.

Repository cleanup auditing works across frontend, backend, and documentation scopes. It locates tracked test outputs, orphaned configs, temporary debug files, and deprecated files within each specific area, returning categorized findings tailored to the technical stack being analyzed.

Root-level leftovers and backup files are tracked due to .gitignore gaps where existing ignore rules fail to match specific file patterns. An audit detects these mismatches and suggests exact lines to add to your .gitignore, preventing unnecessary files from remaining in version control.