Usually, when you want one change in a long text, you tell the AI what to change and hope it stays in its lane. This approach flips that. You ask it what it will leave alone before it changes anything.
Reddit user u/tuckertheo5 shared this in r/PromptEngineering. The problem is a familiar one. You hand Claude a long document and ask for a single edit. It makes the edit, then “improves” a few other lines you never mentioned. A fixed comma here, a reworded sentence there, a heading that suddenly sounds more “professional.” Now you have to hunt for every stray change, and in a 3,000-word document that hunt can take longer than the edit itself.
The key idea
Add a short first step before the edit. Ask Claude to write a list of the parts it will leave exactly as they are. Once you’ve seen the list, tell it to go ahead.
The list works as a commitment. Claude has now said, in its own words, what is off limits. If it strays later, you don’t have to argue about what you meant. You point back to its own line. It also forces the model to actually read the whole text and think about its structure before touching anything, which tends to make the edit itself more focused. The original poster says stray edits dropped a lot after switching to this. That’s one person’s experience, not a benchmark, but the logic is easy to test yourself.
Old way vs. new way
The old way: you describe the change you want and rely on the model to guess the boundaries. Anything you didn’t forbid is fair game, and models like to be helpful. A phrase like “only change the second paragraph” sounds clear to you, but the model may read it as “make the second paragraph fit better with everything around it,” and that is where the drift begins.
The new way: you make the boundaries explicit and get them agreed before any edit happens. Instead of you policing a vague “only change X,” the model writes the rules itself, and you just read them. A typical list might say: “I will not change the intro, the headings, the bullet points, the word choice in paragraphs one and three, or the closing call to action.”
The contrast is simple. The old way tries to control the output after the fact, when you are already comparing two versions line by line. The new way sets the limits first, in a place where you can check them in about ten seconds. Fixing a wrong boundary in a short list is far cheaper than fixing a wrong edit in a long document.
How to try it
- Paste your text and describe the one change you want. Do not ask for the edit yet. Be specific, for example “shorten the third paragraph by about a third.”
- Ask: “Before editing, list the parts of this text you will leave exactly as they are.”
- Read the list. Add anything missing, like “also don’t touch the headings” or “keep my formatting.” Pay special attention to the things models love to tweak: punctuation, capitalization, tone, and the order of items in lists.
- Say “go ahead” once the list looks right.
- If something outside the change shifts, quote Claude’s own line back to it and ask it to restore that part. For example: “You said you would leave the closing paragraph alone, but the second sentence changed. Please put it back exactly as it was.”
A practical tip: if the edit is for code, ask Claude to name the functions and imports it won’t touch. If the edit is for copy, ask it to quote the first few words of each protected section. Quoting makes the list concrete, and it is much easier to spot a gap when you see actual text instead of a general promise.
Where this helps most ✨
- 📄 Long documents where one paragraph needs a fix, such as a report where only the summary is out of date
- 💻 Code files where you want one function changed and nothing else, so your diff stays small and easy to review
- 📝 Copy that has already been approved except for one line, where legal or a client has signed off on everything else
Why it’s worth a try
It costs you one extra message and a few seconds of reading. In return you get a clear record of what was promised, and a much easier time spotting when the model breaks it. You also build a habit of thinking about what should stay the same, which is half of good editing anyway. If you work with long texts, run this on your next edit and compare it with how you did it before.
Have you found other tricks for keeping AI edits tight? Share them in the comments, I’d like to hear what works for you!
Asking Claude to list what it will NOT touch before it edits my file
by u/tuckertheo5 in PromptEngineering