project-audit

Auditing a project directory involves scanning for root-level clutter, measuring runtime and cache sizes, and checking git status to categorize findings into gitignore gaps, archive candidates, and delete candidates for actionable cleanup.

The best way to find stale artifacts is running a scan phase that measures cache sizes and detects root-level clutter, then categorizes them into a structured cleanup plan to execute user-approved deletions safely.

You can determine what to add to gitignore by running an audit that categorizes unused files and runtime directories into gitignore gaps during the scan phase, presenting structured recommendations to selectively update your repository configuration.

Yes, this project cleanup approach applies to any software project repository by scanning for uncommitted changes, stale artifacts, and large runtime directories to guide users through actionable cleanup steps before refactors or onboarding.

You cannot automatically delete unused files without approval during a project audit; the tool presents a structured plan categorizing delete candidates and executes user-approved actions with safety prompts to move items to archive or perform deletions.