cleanup

To safely clean up your project workspace, you can run an audit that identifies temp files, dead code, and build caches. The process uses a dry-run preview to show proposed actions before any destructive changes are applied.

Auditing multiple git repositories for security and hygiene involves scanning workspace categories like git status, dependencies, and code quality. The audit operates across multi-repo environments and generates a final summary with an actionable remediation plan.

Project cleanup safeguards protected paths and will not delete protected files. Before making destructive changes, it offers stash or branch backups, and provides rollback options to revert actions after reviewing the final summary.

The workspace cleanup process supports dry-run previews before modifying dependencies. It enforces safety rules by requiring user confirmation for dependency and build cache actions, ensuring no unintended alterations occur.

An automated project audit is ideal when managing multi-repo environments requiring comprehensive checks across security, dead code, and build caches. It provides category-based workflows and rollback options that manual git cleanup lacks.

To remediate code quality and build cache issues without losing uncommitted work, the audit creates stash or branch backups before taking destructive action. This ensures your uncommitted git changes are safely preserved and reversible.