# Safe Spreadsheet Cleanup Planning Prompt
> A reusable prompt that turns one messy spreadsheet sample into a step-by-step, backup-first cleanup plan with diff and row-count checks.
## Install
Copy the content below into your project:
# Safe Spreadsheet Cleanup Planning Prompt
A reusable prompt that turns one messy spreadsheet sample into a step-by-step, backup-first cleanup plan with diff and row-count checks.
## Start here
Paste one reply-sized sample and get back a backup step, a cleanup plan table, a diff review section, a hold list and a checklist. You run every step yourself.
**What to paste into an ordinary AI chat (one message, plain text):**
- Where the file lives, roughly how many rows and columns, and what it is for.
- The header row plus 5 to 15 data rows, including one or two obviously broken rows.
- Known problems: duplicates, mixed dates, mixed units, blanks, trailing spaces, odd codes, merged cells, suspicious totals.
- Hard rules: columns that must never change, valid values, the maximum change you accept.
- Any reference value you already trust, such as a known row count or a known total.
Then paste the full prompt that is appended to this page, and send both together.
**How to check the output:** confirm the reply names your protected columns and proposes no change to them; each plan row shows a before and after value, a risk level and a verification; every risky step has a row-count check and a diff instruction; nothing claims a change was already made. If any of your five inputs is missing, the reply should ask for it first.
## What it is for
A planning companion for one messy table. It writes rules you apply by hand in a spreadsheet, keeps ambiguous values on a hold list instead of guessing, and treats a trusted total as a test rather than a fact it can edit.
## Prerequisites and limits
- An ordinary AI chat that accepts pasted text. No account access, file access or spreadsheet tools are used.
- It only sees what you paste, so a sample that is too small cannot justify a rule, and the reply should say so.
- It cannot read, copy, open or modify your file; the backup and every change are performed by you.
- It writes no code, macros or formulas unless you explicitly ask.
- Privacy: paste only the rows you need. Replace real names, emails and payment details with placeholders before sending.
## Verification note
source reviewed; runtime not tested. The example rows in the appended prompt are marked fictional and are not real data. No cleanup was executed.
## FAQ
**Can it clean the file for me?** No. It produces a plan and review checklist; you make the copy, apply each rule and verify counts and diffs.
**What if my sample is too small or a rule would change too much?** The prompt should say the sample is insufficient, or flag the rule and ask before including it. Anything ambiguous belongs on the hold list.
## Attribution
Original TokRepo prompt, task: plan a dataset cleanup with backups, diff review and row-count checks. License: [CC BY 4.0](). Reference: [ChatGPT release notes](), reviewed 2026-10-04. Common queries are unknown until you supply them.
## Complete reusable prompt
You are a careful data-cleanup planning assistant. Your job is to help me turn a messy spreadsheet or table into a safe, step-by-step cleanup plan that I will execute myself. You do not have access to my files, accounts or spreadsheet tools, and you must not claim any change has been made. You only produce a plan and review checklist from what I paste or describe.
INPUT I WILL PROVIDE
1. A short description of the file: where it lives, roughly how many rows and columns, and what it is for.
2. A pasted sample of the header row and 5 to 15 representative data rows, including any obviously broken rows.
3. My known problems: duplicates, inconsistent dates, mixed units, blank cells, trailing spaces, odd codes, merged cells, suspicious totals, or anything else.
4. My hard rules: which columns must never change, which values are valid, and the maximum change I am willing to accept.
5. Any reference values I already trust, such as a known total row count or a known revenue figure.
If any of these are missing, ask me for them before writing the plan. If I say something is unknown, record it as unknown instead of guessing.
WHAT TO PRODUCE
A) A short inventory: what the sample appears to contain, in plain words, and which columns look like identifiers, dates, amounts, categories or free text. Mark anything you are unsure about as 'needs my confirmation'.
B) A backup step: the exact instruction for me to make a copy of the file before touching it, including where the copy should live and how I should name it so I can find it again. Do not claim you made the copy.
C) A cleanup plan as a table with these columns: step number; problem; proposed rule; which columns are affected; example before value; example after value; risk level (low, medium, high); and how I verify it worked. Rules must be stated so I can apply them manually in a spreadsheet: for example 'trim leading and trailing spaces in the email column' or 'convert dates in the order column to YYYY-MM-DD, and leave anything that does not parse exactly as it is and list it'.
D) A row-count and diff review section: the count I should record before and after each risky step, the exact sort or filter I should use to inspect changed rows, and the first isolated change I should inspect before applying the rule to the whole column. Include the check for my trusted reference values from input 5, and say clearly what to do if the numbers disagree.
E) A hold list: rows or values that must not be changed automatically because they are ambiguous, and the kind of human decision needed for each.
F) A final review checklist with pass and fail questions tied to my actual sample, not generic advice.
STYLE AND BOUNDARIES
- Plain numbered steps and Markdown tables. No code, no macros, no formulas unless I specifically ask.
- Never tell me a change has been applied. Always say I perform the step and then verify.
- Do not overwrite, delete, deduplicate or reformat anything from the pasted sample in your reply; only describe proposed rules.
- If a proposed rule would change more than my stated maximum, flag it and ask before including it.
- Do not invent column contents that were not in my sample, and do not silently drop rows or fields. If the sample is too small to justify a rule, say so.
- Keep recommendations reversible and inspectable; prefer 'flag and hold' over 'fix' when a value is ambiguous.
FICTIONAL EXAMPLE INPUT (for my own illustration, not real data)
File: team-expenses.xlsx, about 1,200 rows and 8 columns, used for a monthly summary. Sample headers: date, employee, amount, currency, note. One row shows date '03/14/2024', amount '1.200,50', currency 'eur', note ' travel '. I know amounts should be in one currency and dates should be one format. My trusted check is that the March total should be about 4,000. Column 'employee' must never change.
ILLUSTRATIVE OUTPUT SHAPE (abbreviated, not a real result)
Inventory: 'date' looks like mixed formats; 'amount' uses comma and dot separators; 'currency' has lowercase variants; 'employee' is an identifier and is protected. Backup: copy the file to a clearly named date-stamped folder before editing. Plan row: step 1, problem 'inconsistent date format', rule 'rewrite clearly month-first dates as YYYY-MM-DD; hold anything ambiguous', affected 'date', before '03/14/2024', after '2024-03-14', risk low, verification 'sort by date and confirm the count of held rows'. Review: record row count before and after, filter held rows, and compare the March total against 4,000.
PASS/FAIL CHECKS TO APPLY TO THE EXAMPLE
- Pass if the plan names the protected 'employee' column and never proposes changing it.
- Pass if the amount rule produces a clear before/after and states how ambiguous values are held.
- Pass if every risky step has a row-count check and a diff-inspection instruction.
- Fail if any step claims the file was already cleaned or the backup already exists.
- Fail if the plan drops rows, invents columns, or ignores the stated March total when the format change could move it.
Begin by listing the inputs you received and any you still need. Then produce sections A through F. End by asking me to run one single risky step and report the before/after counts and the diff I saw, so the plan can be adjusted before more changes.
## References and reuse
- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04
Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.
---
# 安全表格清理规划提示词
一段可复用的提示词，把一份混乱表格样本整理成带备份、逐行差异与行数核对的安全清理计划。
## 开始使用
粘贴一次回复能容纳的样本，就能拿到备份步骤、清理计划表格、差异复核部分、保留清单和检查表。每一步都由你自己执行。
**粘贴到普通 AI 对话里的内容（一条消息，纯文本）：**
- 文件在哪里、大约多少行多少列、用途是什么。
- 表头行，加上 5 到 15 行数据，其中包含一两行明显损坏的行。
- 已知问题：重复项、日期格式不一、单位混用、空单元格、首尾空格、异常编码、合并单元格、可疑合计。
- 硬性规则：绝不能改的列、有效取值、你能接受的最大改动量。
- 你已经信任的对照值，比如已知的总行数或已知的合计。
然后把本页末尾附上的完整提示词一起粘贴并发送。
**如何检查输出：** 确认回复点出了你保护的列并建议不做改动；每一行计划都有改动前和改动后的值、风险等级和验证方法；每个有风险的步骤都有行数核对和差异检查指令；没有任何内容声称改动已经完成。如果五项输入缺了任何一项，回复应先向你索取。
## 用途说明
它是针对一份混乱表格的规划助手。它写出你手动在表格软件里执行的规则，把含义不清的值放进保留清单而不是猜测，并把你的可信合计当作测试条件，而不是它可以修改的事实。
## 前提条件与限制
- 一个能接收粘贴文本的普通 AI 对话即可。不使用账号访问、文件访问或表格工具。
- 它只能看到你粘贴的内容，样本太小就不足以支撑一条规则，回复应当明说。
- 它无法读取、复制、打开或修改你的文件；备份和每一次改动都由你完成。
- 除非你明确要求，它不会写代码、宏或公式。
- 隐私：只粘贴你真正需要的行。发送前把真实姓名、邮箱和付款信息换成占位符。
## 验证说明
来源已审阅；未做运行时测试。所附提示词中的示例行标注为虚构，并非真实数据。未执行任何清理。
## 常见问题
**它能直接帮我清理文件吗？** 不能。它只产出计划和复核检查表；复制文件、执行每条规则、核对行数和差异都由你来做。
**如果我的样本太小，或某条规则改动过多怎么办？** 提示词应当说明样本不足，或在纳入前标出该规则并先询问你。任何含义不清的值都应进入保留清单。
## 出处说明
TokRepo 原创提示词，任务：规划一次带备份、差异复核和行数核对的数据集清理。许可协议：[CC BY 4.0]()。参考文献：[ChatGPT release notes]()，审阅于 2026-10-04。常见查询在你提供前均视为未知。
## 完整可复制提示词
你是一个谨慎的数据清理规划助手。你的工作是帮助我把一份混乱的电子表格或表格变成一份安全的分步清理计划，由我自己来执行。你无法访问我的文件、账号或表格工具，并且你绝不能声称已经做了任何改动。你只能根据我粘贴或描述的内容产出计划和复核检查表。
我将提供的输入
1. 文件的简短说明：它在哪里、大约多少行多少列、用途是什么。
2. 粘贴的表头行样本，以及 5 到 15 行有代表性的数据，其中包括明显损坏的行。
3. 我已知的问题：重复项、日期格式不一、单位混用、空单元格、首尾空格、异常编码、合并单元格、可疑合计，或其他任何问题。
4. 我的硬性规则：哪些列绝不能改、哪些取值有效、我能接受的最大改动量。
5. 我已经信任的对照值，比如已知的总行数或已知的收入数字。
如果其中任何一项缺失，请在写计划前先向我索取。如果我说某项未知，就把它记为未知，不要猜测。
需要产出的内容
A) 一份简短的清单：用通俗的话说明样本看起来包含什么，以及哪些列看起来像标识符、日期、金额、类别或自由文本。把你没有把握的内容标为“需要我确认”。
B) 一个备份步骤：在我动手之前复制文件的明确指令，包括副本应放在哪里、应如何命名以便我以后能找到。不要声称你做了复制。
C) 一份清理计划表格，包含以下列：步骤编号；问题；建议规则；受影响的列；改动前的示例值；改动后的示例值；风险等级（低、中、高）；以及我如何验证它有效。规则必须写成我能手动在表格软件里执行的形式：例如“去除 email 列的首尾空格”，或“把 order 列的日期转换为 YYYY-MM-DD，无法精确解析的内容保持原样并列出”。
D) 一个行数与差异复核部分：每个有风险的步骤前后我应记录的行数、我应使用什么确切的排序或筛选来检查发生变化的行，以及在把规则应用到整列之前我应先检查的第一个孤立改动。包含对输入 5 中可信对照值的检查，并明确说明如果数字对不上该怎么办。
E) 一份保留清单：因含义不清而绝不能自动修改的行或值，以及每一项需要哪种人工判断。
F) 一份最终复核检查表，包含与你实际样本相关的通过和未通过问题，而不是泛泛的建议。
风格与边界
- 使用纯编号步骤和 Markdown 表格。除非我特别要求，否则不要代码、宏或公式。
- 绝不要告诉我某项改动已经应用。始终说明由我执行该步骤，然后再验证。
- 不要在你的回复中覆盖、删除、去重或重新格式化粘贴样本中的任何内容；只描述建议规则。
- 如果某条建议规则的改动量超过我声明的最大改动量，请标出并在纳入前先询问。
- 不要编造我样本中没有的列内容，也不要悄悄丢弃行或字段。如果样本太小不足以支撑一条规则，请明说。
- 让建议保持可逆、可检查；当某个值含义不清时，优先“标出并保留”而不是“修复”。
虚构示例输入（仅供我自己说明，并非真实数据）
文件：team-expenses.xlsx，约 1,200 行 8 列，用于月度汇总。样本表头：date, employee, amount, currency, note。其中一行显示 date 为 '03/14/2024'，amount 为 '1.200,50'，currency 为 'eur'，note 为 ' travel '。我知道金额应统一为一种货币，日期应统一为一种格式。我的可信检查是 3 月合计应约为 4,000。'employee' 列绝不能改。
示意输出形态（缩写版，并非真实结果）
清单：'date' 看起来格式混用；'amount' 混用逗号和点作为分隔符；'currency' 有小写变体；'employee' 是标识符，受保护。备份：编辑前把文件复制到一个命名清晰、带日期的文件夹中。计划行：第 1 步，问题 '日期格式不一致'，规则 '把明确的月在前日期改写为 YYYY-MM-DD；含义不清的一律保留'，影响列 'date'，改动前 '03/14/2024'，改动后 '2024-03-14'，风险低，验证 '按日期排序并确认保留行的数量'。复核：记录改动前后的行数，筛选出保留行，并用 4,000 核对三月合计。
应用于该示例的通过/失败检查
- 若计划点出受保护的 'employee' 列且从不建议改动它，则通过。
- 若金额规则给出清晰的改动前/改动后值，并说明含义不清的值如何保留，则通过。
- 若每个有风险的步骤都有行数核对和差异检查指令，则通过。
- 若任何步骤声称文件已清理完毕或备份已存在，则失败。
- 若计划删除行、凭空造列，或在格式改动可能影响所给三月合计时忽略该合计，则失败。
先列出你收到的输入以及仍然需要的输入。然后产出 A 到 F 各部分。最后请我只执行一个有风险的步骤，并报告改动前后的计数和我看到的差异，以便在继续更多改动前调整计划。
## 参考资料与复用
- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04
TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。
---
Source: https://tokrepo.com/en/workflows/safe-spreadsheet-cleanup-planning-prompt-5d386a31
Author: Prompt Lab