tidying-files

To safely remove OS cruft across repositories, run a dry-run cleanup to preview deletions, then execute with the --fix option to delete only untracked, non-submodule junk files like .DS_Store and editor backups.

Yes, you can delete untracked junk files fleet-wide without removing git-tracked work because the cleanup process checks git-tracked status and submodule boundaries, ensuring only ignored or untracked OS cruft is targeted.

The best way to automate periodic cleanup of OS cruft is using a /loop cadence to schedule conservative, no-prompt maintenance that keeps repositories tidy by regularly removing accumulated editor backups and untracked files.

The fleet cleanup process performs a dry-run by default to preview which untracked junk files will be deleted, requiring an explicit --fix option to authorize and execute the actual deletions across the fleet.

Cleaning up OS cruft will not affect your git submodules because the cleanup mechanism explicitly checks submodule boundaries, ensuring submodule contents remain untouched while only removing untracked junk files.

To preview which junk files will be removed before a fleet-wide cleanup, execute the tidy-files script in its default dry-run mode, which lists all targeted untracked files without deleting them until --fix is passed.