work-clean

Automated dead code detection in Node.js or Rust projects is handled by scanning files with tools like knip, depcheck, and cargo-udeps to identify unused exports, functions, and variables for removal. The Skill categorizes deletions into SAFE, CAUTION, and DANGER levels, only auto-deleting SAFE modifications.

Cleaning up unused dependencies and imports is best done by scanning project manifests and files to detect and remove redundant code patterns. This Skill targets Node.js, Rust, Go, and Python environments, ensuring code safety by categorizing changes into SAFE, CAUTION, and DANGER levels before applying automated deletions.

Yes, automated code cleanup works with Go and Python projects, utilizing tools like go mod tidy for dependency analysis and scoping. It detects dead code, unused imports, and duplicate patterns across these project files while categorizing all suggested modifications into SAFE, CAUTION, and DANGER levels.

Automated dead code deletion is kept safe by categorizing all detected changes into SAFE, CAUTION, and DANGER levels. The Skill only performs automated deletion for modifications classified as SAFE, ensuring that uncertain or potentially breaking code changes require manual review.

You should run a code cleanup scan after completing a feature to ensure no leftover dead code, unused imports, or unnecessary dependencies are included in the final commit. This prevents code duplication and maintains a cleaner, more maintainable codebase across Node.js, Rust, Go, and Python projects.