← IndexEntry № 191·writing

Proofread and Line-Edit With Tracked Corrections

Performs a careful proofread and line edit with corrected text plus a categorized change log.

Optimized for
ChatGPTClaude
§ When to use this

Proofreading your own work is famously hard, your brain reads what you meant, not what's on the page. This prompt gives you a second set of eyes that catches the mechanical errors (grammar, spelling, punctuation, agreement, tense) plus the line-level awkwardness that spell-checkers miss. The key discipline is restraint: it fixes errors and smooths clunky sentences without rewriting content you didn't ask it to touch, so your voice survives the edit. The numbered change log, grouped by error type, turns each pass into a mini lesson; if you keep seeing the same comma splice flagged, you've found a habit worth fixing at the source. It also separates clear errors from judgment calls by flagging unclear sentences for you to decide rather than silently rewording them. Set your [STYLE GUIDE] and [SPELLING] so it enforces the right conventions, AP versus Chicago, US versus UK, instead of guessing.

§ The Prompt— fill in the fields, then copy or open in a tool
§ Customize0/4 fields filled
your prompt — fill the fields above
You are a meticulous proofreader and line editor. Review the text below for grammar, spelling, punctuation, agreement, tense consistency, and awkward phrasing. Fix errors and smooth clunky sentences without changing the author's meaning or [VOICE]. Follow [STYLE GUIDE] conventions and [SPELLING] spelling.

Return three things: (1) the fully corrected text, (2) a numbered change log grouping fixes by type with brief reasons, and (3) any sentences you flagged as unclear but left for the author to decide. Do not rewrite content you weren't asked to change.

Text:
[PASTE TEXT]
Open with your prompt →ChatGPTClaudeSends your filled-in prompt straight into a new chat.
§ Example Output

What you can expect back

Corrected: The team has been working on the project since March, and there is a lot of progress to report. The launch is planned for Q3.

Change log:
1. Agreement: 'The team have' -> 'The team has' (collective noun takes singular in AP/US usage).
2. Spelling: 'their is' -> 'there is'; 'alot' -> 'a lot.'
3. Punctuation: split a comma splice ('...report, the launch...') into two sentences.

Flagged for author: 'a lot of progress to report' is vague, consider naming a concrete milestone, but I left your wording since changing it alters meaning.

Illustrative example — your results will vary by tool and inputs.

§ Pro Tips

Get sharper results

  • 01Paste a clean copy with no tracked changes; markup confuses the model and muddies the change log.
  • 02If voice matters, give a one-line voice sample so it doesn't 'correct' deliberate fragments or your style.
  • 03Treat flagged-but-not-fixed sentences as the real value; those are the judgment calls only you can make.
  • 04For long documents, edit in sections of a few hundred words so nothing gets skimmed or skipped.
§ Variations

Adapt it for your case

Errors-only

Restrict it to mechanical corrections with zero stylistic smoothing when you want to preserve voice exactly.

Severity-ranked

Ask it to label each change as must-fix, should-fix, or optional so you can triage fast.

Inline marks

Request changes shown inline with [brackets] around edits so you can review each in context before accepting.

Use For — Tasks
Tags#proofreading#line-editing#grammar
§ FAQ

Common questions

Will it rewrite my whole piece?

No. The prompt limits it to fixing errors and smoothing clunky sentences, and bars rewriting content you didn't flag. If it overreaches, add 'errors only, no rephrasing.'

Can it replace a human proofreader?

For most everyday writing, it catches the bulk of errors. For high-stakes or published work, use it as a strong first pass and still have a human verify.

Why does it leave some sentences unfixed?

Because they're unclear in a way only you can resolve, the meaning is ambiguous. It flags rather than guesses, so it never silently changes what you meant.

§ Related Entries

You may also need