Stale File Cleanup

To identify stale files in a repository, classify files based on modification dates, import statements, and package.json references. This flags outdated documentation or unused scripts that are no longer referenced by active code.

Repository file classification works by analyzing modification dates and import mappings to categorize files as required, stale, duplicate, generated, irrelevant, or needing a move for evidence-based code hygiene auditing.

The best way to clean up duplicate and generated files is to audit the repository to classify files based on active references and modification dates, providing evidence-based actions before suggesting deletion or movement.

Yes, you can use this stale file cleanup approach without external dependencies. It operates independently using internal scripts and references to analyze file modification dates and import mappings within your repository.

Yes, the file auditing process requires concrete evidence before suggesting deletion or movement. It checks modification dates, import statements, and active skill mappings to ensure no critical files are lost.

You should not use automated file classification when your repository lacks clear import statements, package.json references, or modification date tracking, as the tool relies on this evidence to prevent the loss of critical files.