Safe File Organizer

Problem

Local directories often mix documents, images, source files, archives, and videos. Manual moving can miss nested folders, overwrite same-name files, or leave a half-finished state after a permission error. file-organizer treats classification as a previewable, confirmable, and rollback-safe file-management action.

How It Works

• Scan and preview: Reads the target folder, processes the current directory by default, and uses -r / --recursive for subdirectories. It skips built-in paths such as node_modules, .git, and __pycache__, and can read .organizer-ignore for user-defined patterns.
• Extension-based sorting: Groups files into Documents, Images, Code, Archives, Video, and Other; .organizer-rules.json can merge custom category rules.
• Two-phase execution: Shows quantity and size before acting, then pre-checks accessibility, ambiguous classification, and destination conflicts before moving. Failures trigger rollback.
• Undo and audit: Generates .organizer-manifest.json, .organizer-log.md, and cross-platform undo scripts, with --rollback for restoration.

Limits

Best for personal project trees, download folders, or document libraries that need bulk categorization. It does not inspect file content or infer semantic ownership; for deeply nested, locked, or permission-restricted trees, use --preview first.