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 加入)。