# Folder Cleanup Plan as a Dry-Run Manifest

> Plan a folder cleanup before touching anything: a dry-run manifest with per-file actions, confidence levels and open questions.

## Install

Copy the content below into your project:

# Folder Cleanup Plan as a Dry-Run Manifest

Plan a folder cleanup before touching anything: a dry-run manifest with per-file actions, confidence levels and open questions.

## Start here

Paste a plain-text inventory of one folder into any AI chat that accepts text. No terminal, API key or installation is needed. This prompt only plans; it cannot see, move, rename, back up or delete your files.

**Input to paste (replace with your own):** one line per item, in the form `FileName | Type | Size | Date modified | Short note`. Add subfolders as top-level lines only. Do not paste file contents unless a name is ambiguous. For large folders, send batches of 40 and wait before the plan is finalized. A fictional shape example:

```
2026-03 receipt.pdf | PDF | 210 KB | 2026-03-04 | utility bill
notes.txt | TXT | 3 KB | 2026-01-18 | meeting notes
```

**How to use it:** paste the full prompt below, then paste your inventory. Or paste the inventory first, then the prompt.

**Check the output:** every manifest row must map back to a line you supplied (no phantom files). Low-confidence and unresolved items must reappear in the questions section. Any delete suggestion must be labelled for your manual confirmation. The prompt should also state your next step: review the manifest, then back up the folder before any change.

## Setup and permissions

Nothing to install, and no account beyond your chat tool. The prompt requests no file access: it works entirely from text you type or paste. It therefore needs a filled-in inventory; entries missing a required field stay in an Unresolved list instead of being guessed. It cannot open, scan or back up anything, and it must not invent dates, sizes, contents or file relationships. Folder names should stay short and portable across operating systems, and renames that may break links should be flagged as a risk. Actions are split into reversible ones (Keep, Move, Rename) and irreversible ones (Delete), and a file may only be marked Delete-Candidate if you explicitly asked to identify deletions — and even then only for your manual confirmation.

## FAQ

**Can it delete or rename my files?** No. It can only revise the plan. You carry out every change yourself, after reviewing the manifest and backing up the folder.

**What if my inventory is incomplete?** Entries missing a needed field go to the Unresolved list with a question, rather than being classified by guesswork, and the prompt should tell you which files cannot be classified before anything is touched.

## Source and thanks

Source reviewed; runtime not tested — no model run, fixture or real cleanup was performed, and the fictional example exists only to show the expected row shape. Original TokRepo prompt, licensed CC BY 4.0. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>) (reviewed 2026-10-04). The complete immutable prompt and its Chinese translation are appended separately.

## Complete reusable prompt

You are helping me plan a folder cleanup before anything on my computer is changed. There is no automatic access here: you cannot see my folders, and pasting this prompt cannot move, rename or delete anything. We are only preparing a plan I will review and carry out myself.

MY INPUT
I will paste an inventory of a single folder. Each entry should look like: FileName | Type | Size | Date modified | Short note about what it is. Include subfolders only as a top-level line, and do not paste file contents unless a name is ambiguous. If I have many files, split the inventory into batches of 40 and tell me to send the next batch before you finalize.

YOUR TASK
1. Read only the inventory I provide. If any entry lacks a needed field, keep the file in an 'Unresolved' list rather than guessing what it is.
2. Propose a target folder structure with short, consistent folder names and a one-line purpose for each folder.
3. Create a dry-run manifest: one row per file with Current path, Proposed path, Action (Keep/Move/Rename/Archive-Elsewhere/Delete-Candidate/Review), Confidence (High/Medium/Low), Reason, and any conflict.
4. Flag duplicates, near-duplicates or version chains (for example report_final vs report_final_v2) only when you can justify the match from the names, dates and sizes I gave.
5. Separate reversible actions (Keep, Move, Rename) from irreversible ones (Delete). Never put a file in Delete-Candidate unless I explicitly asked to identify deletions, and even then mark it for my manual confirmation.
6. Produce a short 'Questions before I touch anything' list for files you cannot classify.

OUTPUT FORMAT
- Section 1: Proposed folder tree, with one-line purpose per folder.
- Section 2: Dry-run manifest table, sorted by target folder, using the columns above.
- Section 3: Unresolved items and questions.
- Section 4: A manual alternative: brief step-by-step instructions for someone doing this without an AI tool, including how to copy the manifest into a spreadsheet and sort it themselves before editing.

RULES
- Do not claim you have opened, scanned or backed up my files.
- Do not invent dates, sizes, contents or file relationships that are not in my inventory.
- If I ask you to go ahead and make changes, restate that you can only revise the plan.
- Keep names short and usable across operating systems: avoid characters that are often invalid, and avoid renaming files in ways that break links unless you note the risk.

FICTIONAL EXAMPLE INPUT (for shape only)
2026-03 receipt.pdf | PDF | 210 KB | 2026-03-04 | utility bill
2026-03 receipt (1).pdf | PDF | 210 KB | 2026-03-04 | same bill
notes.txt | TXT | 3 KB | 2026-01-18 | meeting notes
client_logo_final_v2.png | PNG | 480 KB | 2025-11-30 | logo

For that example, a good manifest would map the two receipt files to a Receipts/2026 folder with one marked as a likely duplicate for me to confirm, keep notes.txt in Notes, and place the logo in a Design/ClientAssets folder with a note that the '_v2' suffix may be a final version. A wrong answer would silently delete one receipt, guess the logo is unused, or rename notes.txt without saying why.

CHECKS BEFORE YOU FINISH
- Every manifest row traces to an entry I supplied; no phantom files.
- Every Low-confidence or unresolved row appears again in Section 3.
- No Delete-Candidate row without an explicit note that I must confirm it manually.
- Folder names are consistent and do not exceed a sensible depth of two or three levels.
- Tell me the next action I should take myself: review the manifest, then back up the folder before any changes.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 用试运行清单规划文件夹整理

动手前先做文件夹清理计划：试运行清单逐条给出操作、置信度和待确认问题，不进目录、不改文件。

## 开始使用

把单个文件夹的纯文本清单粘贴进任何支持文本的 AI 对话即可。不需要终端、API 密钥或安装。这段提示词只负责规划，它无法查看、移动、重命名、备份或删除你的文件。

**要粘贴的输入（请替换成你自己的内容）：** 每项一行，格式为 `FileName | Type | Size | Date modified | Short note`。子文件夹只作为顶层行列出。除非名称有歧义，不要粘贴文件内容。文件很多时，先发送一批 40 条，等提示词确认后再继续。虚构形式示例：

```
2026-03 receipt.pdf | PDF | 210 KB | 2026-03-04 | utility bill
notes.txt | TXT | 3 KB | 2026-01-18 | meeting notes
```

**如何使用：** 先粘贴下面的完整提示词，再粘贴你的清单；也可先粘贴清单，再粘贴提示词。

**如何检查输出：** 每一行清单都必须对应你提供的某一条（不能出现凭空文件）。低置信度和未解决项必须再次出现在问题清单中。任何删除建议都必须标注需要你本人确认。提示词还应告诉你下一步：先审阅清单，然后在做任何更改前备份该文件夹。

## 准备工作与权限

无需安装，除了你使用的对话工具外也不需要额外账号。提示词不申请任何文件访问权限：它完全基于你输入或粘贴的文本工作。这也意味着它需要一份填写完整的清单；缺失字段的条目会进入未解决列表，而不是被猜测。它无法打开、扫描或备份任何内容，也不会编造日期、大小、内容或文件关系。文件夹名应保持简短并跨操作系统可用；可能导致链接失效的重命名应标注为风险。操作被分为可逆（保留、移动、重命名）与不可逆（删除）两类；只有在你明确要求识别删除项时，文件才可被标记为删除候选，而且仍须由你本人手动确认。

## 常见问题

**它会删除或重命名我的文件吗？** 不会。它只能修改计划。你需要在审阅清单并备份文件夹之后，自己执行每一步更改。

**如果我的清单不完整怎么办？** 缺少必要字段的条目会带着问题进入未解决列表，而不是靠猜测分类；提示词应告诉你在改动任何内容之前哪些文件无法分类。

## 来源与致谢

已审阅来源；未进行运行时测试——没有运行模型、测试样本或真实清理，虚构示例仅用于展示期望的表格形式。TokRepo 原创提示词，采用 CC BY 4.0 许可。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)（审阅于 2026-10-04）。完整且不可更改的提示词及中文翻译另行附上。

## 完整可复制提示词

你正在帮助我在电脑上的任何内容被更改之前，规划一次文件夹清理。这里不存在自动访问：你看不到我的文件夹，粘贴这段提示词也无法移动、重命名或删除任何内容。我们只是在准备一个由我审阅并亲自执行的计划。

我的输入
我会粘贴一个单一文件夹的清单。每条记录应当形如：FileName | Type | Size | Date modified | 关于它是什么的简短备注。子文件夹只作为顶层行列出，除非某个名称有歧义，否则不要粘贴文件内容。如果我的文件很多，请把清单分成每批 40 条，并在你定稿之前告诉我发送下一批。

你的任务
1. 只读取我提供的清单。如果有任何条目缺少必要字段，请把该文件留在“未解决”列表中，而不是猜测它是什么。
2. 提出一个目标文件夹结构，使用简短、一致的文件夹名称，并为每个文件夹给出一行用途说明。
3. 创建一个试运行清单：每个文件一行，包含当前路径、建议路径、操作（保留/移动/重命名/归档到别处/删除候选/复查）、置信度（高/中/低）、理由，以及任何冲突。
4. 仅当你能够根据我给出的名称、日期和大小证明匹配合理时，才标记重复项、近似重复项或版本链（例如 report_final 与 report_final_v2）。
5. 把可逆操作（保留、移动、重命名）与不可逆操作（删除）分开。除非我明确要求识别删除项，否则绝不要把文件放入删除候选；即便如此，也要标注需要我手动确认。
6. 为你无法分类的文件生成一份简短的“动手之前的问题”列表。

输出格式
- 第 1 部分：建议的文件夹树，每个文件夹附一行用途说明。
- 第 2 部分：试运行清单表格，按目标文件夹排序，使用上述列。
- 第 3 部分：未解决项与问题。
- 第 4 部分：一份不用 AI 的手动替代方案：为不使用 AI 工具的人提供简要的分步说明，包括如何把清单复制到电子表格中并在编辑前自行排序。

规则
- 不要声称你已经打开、扫描或备份了我的文件。
- 不要编造我的清单中不存在的日期、大小、内容或文件关系。
- 如果我要求你直接进行更改，请重申你只能修改计划。
- 保持名称简短且可跨操作系统使用：避免使用经常无效的字符，并避免以会破坏链接的方式重命名文件，除非你注明了风险。

虚构示例输入（仅为展示形式）
2026-03 receipt.pdf | PDF | 210 KB | 2026-03-04 | utility bill
2026-03 receipt (1).pdf | PDF | 210 KB | 2026-03-04 | same bill
notes.txt | TXT | 3 KB | 2026-01-18 | meeting notes
client_logo_final_v2.png | PNG | 480 KB | 2025-11-30 | logo

对于该示例，一份好的清单应把两个收据文件映射到 Receipts/2026 文件夹，并将其中一个标记为可能的重复项供我确认；把 notes.txt 保留在 Notes 中；把 logo 放到 Design/ClientAssets 文件夹，并注明“_v2”后缀可能是最终版本。错误的答案会悄悄删除一张收据、猜测该 logo 未被使用，或在没有说明原因的情况下重命名 notes.txt。

完成前的检查
- 每一行清单都可追溯到我提供的某条记录；没有凭空文件。
- 每一行低置信度或未解决的记录都要再次出现在第 3 部分。
- 没有删除候选行不带明确说明我需要手动确认。
- 文件夹名称一致，且不超过两到三层的合理深度。
- 告诉我我自己应采取的下一步行动：审阅清单，然后在做任何更改前备份该文件夹。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes)

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/folder-cleanup-plan-dry-run-manifest-6c387fae
Author: Prompt Lab