Deleted Files Audit

To check for stale references before committing deleted files in git, audit pending deletions by scanning source code and IDE configurations for lingering imports or paths. This process categorizes deletions and provides a structured safety verdict to prevent broken builds.

Committing a git deletion while the file is still referenced in build scripts causes broken builds and runtime errors. A deleted files audit scans build scripts and source code to detect these lingering references and warns you before the commit is finalized.

Yes, you can categorize pending git deletions by file type such as generated output, source code, or config. The audit classifies deleted files to help you assess the impact of removing generated outputs versus critical source code before committing.

To prevent accidental commits of generated output files in git, check your .gitignore coverage during a deleted files audit. The audit recommends specific .gitignore additions to ensure generated outputs are ignored and excluded from future commits.

Yes, a deleted files audit works as a pre-commit hook for code maintenance by intercepting staged deletions. It scans the codebase for stale references and provides a safety verdict before the commit is applied, ensuring code hygiene.