file-organizer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

File Organizer

文件整理工具

Instructions

操作说明

1. Understand Scope

1. 明确范围

Ask clarifying questions before starting:
  • Which directory needs organization?
  • Main problem? (can't find things, duplicates, no structure, general mess)
  • Files or folders to avoid? (active projects, sensitive data)
  • How aggressive? (conservative vs comprehensive cleanup)
For broad reorganization, briefly propose a philosophy from the reference guide (PARA, Johnny Decimal, GTD, 7-Folder). Let user choose - never force one. Skip for scoped tasks like cleaning Downloads.
开始前先询问澄清问题:
  • 需要整理哪个目录?
  • 主要问题是什么?(找不到文件、存在重复、无结构、整体杂乱)
  • 有哪些文件或文件夹需要避开?(活跃项目、敏感数据)
  • 清理力度如何?(保守型 vs 全面清理)
对于大范围重构,可简要参考指南中的整理理念(PARA、Johnny Decimal、GTD、7-Folder),让用户选择——切勿强制推行。若为限定范围的任务(如清理下载文件夹),可跳过此步骤。

2. Analyze Current State

2. 分析当前状态

bash
ls -la [target_directory]
find [target_directory] -type f -exec file {} \; | head -20
du -sh [target_directory]/* | sort -rh | head -20
find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
Summarize: total files/folders, type breakdown, size distribution, date ranges, obvious issues.
Anti-patterns to flag:
  • Desktop used as permanent archive (goal: zero permanent files on Desktop)
  • Unnamed folders (
    New Folder
    ,
    New Folder (3)
    )
  • Broken versioning (
    document_FINAL_v2_DEFINITIVE_copy.docx
    )
  • Downloads folder never cleaned (thousands of unsorted files)
  • Same file duplicated across locations (use shortcuts instead)
bash
ls -la [target_directory]
find [target_directory] -type f -exec file {} \; | head -20
du -sh [target_directory]/* | sort -rh | head -20
find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
总结内容:文件/文件夹总数、类型分布、大小占比、时间范围、明显问题。
需要标记的不良模式:
  • 将桌面用作永久存档(目标:桌面无永久文件)
  • 未命名文件夹(
    New Folder
    ,
    New Folder (3)
  • 混乱的版本命名(
    document_FINAL_v2_DEFINITIVE_copy.docx
  • 下载文件夹从未清理(数千个未分类文件)
  • 同一文件在多个位置重复存储(建议使用快捷方式替代)

3. Identify Organization Patterns

3. 确定组织模式

By type:
  • Documents (PDF, DOCX, TXT), Images (JPG, PNG, SVG), Videos (MP4, MOV)
  • Archives (ZIP, TAR, DMG), Code/Projects, Spreadsheets (XLSX, CSV), Presentations (PPTX, KEY)
By purpose:
  • Work vs Personal, Active vs Archive, Project-specific, Reference, Temporary/scratch
By date:
  • Current year/month, Previous years, Very old (archive candidates)
Context-specific structures:
  • Photos/Video:
    Year/YYYY-MM_event-location/
    with RAW, Edited, Export subfolders
  • Music:
    Artist/[Year] Album/NN - Track.ext
  • Work projects: numbered prefixes (
    01_Brief/
    ,
    02_Research/
    ,
    03_Assets/
    ,
    04_Deliverables/
    ) with WIP/FINAL_APPROVED separation
  • Finance/personal docs: include expiry dates in filenames (
    passport_exp_2030.pdf
    ), organize by year then type
  • Code: map local paths to remote URLs (
    github.com/username/repo/
    )
See
references/organization-guide.md
for detailed templates.
按类型分类:
  • 文档(PDF、DOCX、TXT)、图片(JPG、PNG、SVG)、视频(MP4、MOV)
  • 压缩包(ZIP、TAR、DMG)、代码/项目、电子表格(XLSX、CSV)、演示文稿(PPTX、KEY)
按用途分类:
  • 工作 vs 个人、活跃中 vs 已归档、项目专属、参考资料、临时/草稿
按日期分类:
  • 当前年/月、往年、超旧文件(归档候选)
特定场景结构:
  • 照片/视频:
    年份/YYYY-MM_活动-地点/
    ,包含RAW、编辑后、导出子文件夹
  • 音乐:
    艺术家/[年份] 专辑/NN - 曲目.ext
  • 工作项目:带编号前缀(
    01_需求文档/
    02_调研资料/
    03_资源文件/
    04_交付成果/
    ),区分WIP(进行中)与FINAL_APPROVED(最终获批)
  • 财务/个人文档:文件名包含过期日期(
    passport_exp_2030.pdf
    ),按年份再按类型组织
  • 代码:本地路径与远程URL映射(
    github.com/username/repo/
详细模板请参考
references/organization-guide.md

4. Find Duplicates

4. 查找重复文件

When requested:
bash
find [directory] -type f -exec md5 {} \; | sort | uniq -d
find [directory] -type f -printf '%f\n' | sort | uniq -d
For each duplicate set: show paths, sizes, dates, recommend which to keep. ALWAYS confirm before deleting. Suggest shortcuts/aliases instead of keeping copies.
当用户有需求时执行:
bash
find [directory] -type f -exec md5 {} \; | sort | uniq -d
find [directory] -type f -printf '%f\n' | sort | uniq -d
对于每组重复文件:展示路径、大小、日期,推荐保留哪一个。删除前必须确认。建议使用快捷方式/别名替代保留副本。

5. Propose Organization Plan

5. 提出整理方案

Present plan before making changes. Include:
  • Current state summary (file count, size, type breakdown, problems found)
  • Anti-patterns detected
  • Proposed folder tree structure
  • Changes to make: new folders, file moves, renames, deletions
  • Files needing user decision (ambiguous placement)
  • Ask for explicit approval before proceeding
在执行更改前先提交方案,内容包括:
  • 当前状态总结(文件数量、大小、类型分布、发现的问题)
  • 检测到的不良模式
  • 拟议的文件夹树结构
  • 待执行的更改:新建文件夹、移动文件、重命名、删除
  • 需要用户决策的文件(放置位置不明确)
  • 执行前需获得用户明确批准

6. Execute Organization

6. 执行整理

After approval, organize systematically.
Rules:
  • Always confirm before deleting anything
  • Log all moves for potential undo
  • Preserve original modification dates
  • Handle filename conflicts gracefully
  • Stop and ask on unexpected situations
File renaming conventions (only when user agrees - never auto-rename):
  • ISO dates:
    YYYY-MM-DD
    for correct alphabetical sort
  • Formula:
    [Date]_[Context]_[Description]_[Version].ext
  • Zero-padded versions:
    v01
    ,
    v02
    (minor:
    v01.1
    )
  • Separators:
    kebab-case
    or
    snake_case
    (never spaces)
  • All lowercase, filenames under 25-30 chars, let folder context provide the rest
  • Zero-pad sequences:
    001
    ,
    002
    (prevents
    1, 10, 11, 2
    sort)
  • Status prefixes when useful:
    WIP_
    ,
    DRAFT_
    ,
    REVIEW_
    ,
    APPROVED_
  • Avoid:
    < > : " / \ | ? *
    , accents, emoji, leading dots, Windows reserved names (
    CON
    ,
    PRN
    ,
    AUX
    ,
    NUL
    )
  • Watch full path length approaching Windows 260-character limit
获得批准后,系统地进行整理。
规则:
  • 删除任何内容前必须确认
  • 记录所有移动操作,以便后续撤销
  • 保留原始修改日期
  • 妥善处理文件名冲突
  • 遇到意外情况时暂停并询问用户
文件重命名规范(仅在用户同意时执行——切勿自动重命名):
  • ISO日期格式:
    YYYY-MM-DD
    ,确保按字母顺序排序正确
  • 格式:
    [日期]_[上下文]_[描述]_[版本].ext
  • 带前导零的版本号:
    v01
    ,
    v02
    (小版本:
    v01.1
  • 分隔符:
    kebab-case
    snake_case
    (禁止使用空格)
  • 全小写,文件名长度控制在25-30字符以内,由文件夹上下文补充其余信息
  • 带前导零的序列:
    001
    ,
    002
    (避免出现
    1, 10, 11, 2
    的排序问题)
  • 必要时添加状态前缀:
    WIP_
    ,
    DRAFT_
    ,
    REVIEW_
    ,
    APPROVED_
  • 避免使用:
    < > : " / \ | ? *
    、特殊字符、表情符号、前导点、Windows保留名称(
    CON
    ,
    PRN
    ,
    AUX
    ,
    NUL
  • 注意路径总长度接近Windows 260字符限制的情况

7. Provide Summary

7. 提供总结

After organizing, report:
  • Folders created, files organized, space freed, anti-patterns fixed
  • New folder tree structure
  • Maintenance schedule (below)
  • Custom bash commands for ongoing cleanup
Maintenance Schedule:
FrequencyTimeTasks
Weekly15 minEmpty Downloads, process Inbox to zero, verify recent files are in place
Monthly45 minScan for duplicates, verify backups, archive completed projects
Quarterly2 hrsDisk space audit, archive projects inactive 3+ months, test backup restore
YearlyHalf dayDisaster recovery test, retention policy review, structure update
整理完成后,提交报告:
  • 新建文件夹数量、已整理文件数量、释放空间大小、已修复的不良模式
  • 新的文件夹树结构
  • 维护计划(如下)
  • 用于日常清理的自定义bash命令
维护计划:
频率时长任务
每周15分钟清空下载文件夹、处理收件箱至零未处理、验证近期文件是否归位
每月45分钟扫描重复文件、验证备份、归档已完成项目
每季度2小时磁盘空间审计、归档已闲置3个月以上的项目、测试备份恢复
每年半天灾难恢复测试、审查保留策略、更新目录结构