Proofreading & Editing Prompt (LLaMA / Ollama)
This prompt treats editing as a collaboration rather than a rewrite. The change log is the most important feature — it lets you accept or reject individual edits and understand why each change was made, preserving your editorial control. The preserve field prevents the AI from stripping out the personality or specific terms that make your writing distinctive. This variant is formatted for LLaMA / Ollama: Optimised for LLaMA 3, Mistral, and Ollama local models. Uses [INST] / <<SYS>> instruction format.
[INST] <<SYS>>
You are a helpful, accurate, and detailed AI assistant. Follow the instructions carefully.
<</SYS>>
You are a professional copy editor. Edit the following text according to these instructions:
Target style: {{style_guide}}
Audience: {{audience}}
Goals: {{goals}}
Do NOT change: {{preserve}}
Return the output as:
1. **Edited text** — the corrected version in full
2. **Change log** — a bullet list of the significant changes made and why
Text to edit:
{{text}} [/INST]Variables
{{style_guide}}Style rules to follow, e.g., "AP Style", "Chicago", "British English, Oxford comma", or "none"{{audience}}Who will read this text{{goals}}Editing priorities, e.g., "improve clarity and reduce word count by 20%", "fix grammar only"{{preserve}}What should not be changed, e.g., "the author's voice and humour", "technical terminology"{{text}}The text to be editedExample
style_guide: American English, no Oxford comma audience: software developers reading a technical blog goals: improve clarity and fix grammar errors preserve: the casual tone and code examples text: When your dealing with async operations its easy to loose track of errors. You want to always handle rejections or you'll get unhandled promise rejection warnings in Node that can crash your app.
**Edited text:** When you're dealing with async operations, it's easy to lose track of errors. Always handle rejections, or you'll get unhandled promise rejection warnings in Node that can crash your app. **Change log:** - "your dealing" → "you're dealing" — grammatical error (contraction vs. possessive) - "its easy" → "it's easy" — missing apostrophe - "loose" → "lose" — common spelling confusion - Removed "You want to" — unnecessary filler; the direct instruction is clearer
Related Tools
FAQ
- Can I use this to improve non-native English writing?
- Yes. Add to goals: "fix grammatical errors common in non-native English, particularly article usage (a/an/the) and subject-verb agreement". The AI handles these patterns very reliably.
- Will the AI significantly change my writing style?
- It depends on the goals field. If you specify "fix grammar only", the AI makes minimal changes. If you specify "rewrite for clarity", it may restructure sentences significantly. Use the change log to track what changed.
- Can I edit code comments or technical documentation with this?
- Yes. Set style_guide to "technical documentation" and preserve to "all code snippets and technical terminology". The AI will edit the surrounding prose while leaving code blocks untouched.
Related Prompts
This prompt treats editing as a collaboration rather than a rewrite. The change log is the...
Proofreading & Editing Prompt (ChatGPT)This prompt treats editing as a collaboration rather than a rewrite. The change log is the...
Proofreading & Editing Prompt (Claude)This prompt treats editing as a collaboration rather than a rewrite. The change log is the...
Proofreading & Editing Prompt (Gemini)This prompt treats editing as a collaboration rather than a rewrite. The change log is the...
Blog Post Outline & Draft PromptBlog posts generated without structure guidance tend to produce generic, meandering conten...
Text Summarisation PromptSummaries fail when the AI does not know what the reader already knows or what they need t...