I haven't changed anything yet. Here is the plan for your approval.
Current state
Downloads holds 14 loose files plus current-project/, which I'll leave alone. Every file is a small .txt stub, and the real type is in the name (for example IMG_2201.jpg.txt). I'm sorting by that inner type.
Proposed structure (all moves, no deletes)
Downloads/
├── Documents/
│ ├── lease-agreement-2024.pdf.txt
│ ├── sales-report-q3.pdf.txt
│ ├── board-deck-v3.pptx.txt
│ └── pasta-recipe.docx.txt
├── Images/
│ ├── IMG_2201.jpg.txt
│ ├── IMG_2202.jpg.txt
│ └── Screenshot 2026-09-12 at 10.04.11.png.txt
├── Installers/
│ ├── Zoom-installer.dmg.txt
│ └── node-v22-installer.pkg.txt
├── Archive/
│ ├── backup-2022-03.zip.txt
│ └── backup-2022-09.zip.txt
├── To-Sort/
│ ├── untitled.txt
│ ├── sales-report-q3 (copy).pdf.txt (duplicate, see below)
│ └── board-deck-v3 (1).pptx.txt (duplicate, see below)
└── current-project/ (untouched)
The moves keep every filename and modification time, and I'll log each one so it can be undone.
Duplicates (decision for you, nothing is deleted)
These pairs have identical content:
sales-report-q3.pdfandsales-report-q3 (copy).pdfboard-deck-v3.pptxandboard-deck-v3 (1).pptx
Both "(copy)" and "(1)" files look like download leftovers. I'd park them in To-Sort/ rather than delete them. Tell me if you want them deleted.
Three other pairs also have identical content, but I'm not calling them duplicates:
IMG_2201andIMG_2202backup-2022-03andbackup-2022-09Zoom-installerandnode-v22-installer
They have different names and purposes, and these files are only short text stubs. If they were real files with matching hashes, they'd be duplicates. I'm keeping both of each pair.
Questions
- Should the duplicate "(copy)" and "(1)" files go to
To-Sort/(my default), or be deleted? - The 2022 backups are old. Is
Archive/fine, or should they go somewhere else? untitled.txtis "random notes". IsTo-Sort/fine?- Do you want the
.txtsuffixes stripped from the names? I've left them as they are.
Reply "yes" to go ahead with the plan as written, or tell me what to change.
Real run recorded with claude-code / claude-sonnet-5-5. Run on a sample Downloads folder with 14 messy files (the contents are placeholder text; the file names carry the real types). It first proposed a plan and waited for approval, so no file was touched and the demo shows only the plan. Tool-call lines show only the first line of each command. The model output is unmodified.
它做什么
帮你清理下载、文档、项目目录这类文件夹:先了解里面有什么,提出整理结构,找出重复文件和陈旧文件,在你批准后执行。
工作方式
- 先问清楚:整理哪个文件夹、主要问题是什么、哪些不要动、要多激进。
- 概览文件夹(类型、大小、日期),并按内容哈希查找重复文件。
- 给出方案:拟议的结构、每一步移动,以及需要你决定的文件。
- 批准后才移动、重命名,保留修改时间,记录每一次移动以便撤销,删除前一定先问。
适合场景
乱成一团的下载文件夹、散落各处的文件、重复文件,以及归档旧项目。
需要了解
我们试用时,在你批准之前它什么都没改:给出了完整方案,没碰被保护的文件夹,疑似重复的文件放进待处理文件夹而不是直接删除。
纯指令文件:没有脚本。 在你批准方案后,它会运行 shell 命令,在你的电脑上新建文件夹、移动和重命名文件,并在你同意时删除重复文件。请谨慎选择文件夹,重要文件先备份,并告诉它哪些目录不要碰。它的设计是删除前先询问、并记录每次移动。 原 skill 目录没有单独的协议文件,协议依据是来源仓库 README 对整个仓库的 Apache-2.0 声明(同时注明个别 skill 可能不同)。 压缩包里另有 LICENSE(Apache-2.0 全文)和 SOURCE.txt(来源与协议依据说明,由 AIBars 添加)。