Workspace Cleanup Skill

To clean up temporary test scripts and log files, you can run an automated workspace cleanup that detects specific file patterns like test_*.js, *.log, and temp_* in your project root and backend folders, then moves them to a .trash directory.

Organizing a cluttered project root and backend directory involves archiving temporary files, debug logs, and test scripts into a designated .trash folder, which maintains workspace hygiene and keeps active directories clear of unnecessary clutter.

Workspace cleanup works by targeting specific file types, automatically detecting and archiving files matching patterns like test_*.js, *.log, and temp_* to a .trash directory within your development environment.

You can use automated file archiving to safely manage temporary files without manual deletion, as the cleanup process identifies and moves test scripts and debug logs to a .trash directory for later review or removal.

You should run a workspace cleanup script after executing several verification scripts or debugging sessions, ensuring that temporary test_*.js files and debug *.log files are archived to keep your development environment organized.