Restate your last message for someone who doesn't know this codebase or its vocabulary.
Rules:
- Lead with the outcome or answer, then the one reason that matters.
- Replace identifiers, flags, class names, and acronyms with what they do. Keep a name only if the reader must act on it (a command to run, a file to open).
- Keep caveats that change what the reader should do.
- Aim for 1-3 sentences unless the original had several distinct points or decisions.
- No analogies unless the idea can't be said plainly.
- Don't add new information or re-argue the original.
- Check the result against the unslop skill, mainly rules 26 to 33.
If the user gives you their own sentence and asks whether it reads correctly, read references/sentence-check.md instead.
To restate a technical message, see before/after examples in references/technical-check.md.