Menu
Fix grammar and clarity in any text while making the absolute minimum number of changes and preserving as much original wording as possible.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Plan coding work as a compact implementation-step bundle with a conservative research decision, high-level overview first, and planning artifacts written only under .project_planning/YYYY-MM-DD_FEATURE_NAME/. This skill plans only — it never writes, edits, or refactors implementation code, and never skips ahead to building. If only the skill name is given, ask for a high-level description first before writing planning files.
Execute an approved coding plan as serial-first implementation steps with tight scope control, planner-defined verification strategy, and mandatory sub-agent/worktree execution.
Review coding changes against the approved plan, identify concrete bugs, regressions, and plan-adherence gaps, run approved isolated fix passes, then close the loop with optional planning-doc cleanup and PR/MR creation.
Execute an approved coding plan in staged steps with tight scope control, planner-defined verification strategy, deferred automated verification by default, and mandatory isolated sub-agent dispatch when the runtime supports safe worktree execution.
Close out a completed coding loop by validating final chain readiness, checking for leftover repository state, and optionally preparing and creating a PR or MR when the remote provider is supported.
Plan coding work in stages with a mandatory research-decision checkpoint, a high-level overview first, and planning artifacts written only under .project_planning/YYYY-MM-DD_FEATURE_NAME/. If only the skill name is given, ask for a high-level description first before writing any planning files.
| name | copy-polisher |
| description | Fix grammar and clarity in any text while making the absolute minimum number of changes and preserving as much original wording as possible. |
Minimum intervention. The author wrote something. Fix what is broken. Leave everything else alone.
This is not an invitation to improve, rephrase, or elevate the text. It is a grammar and clarity pass. The output should look almost identical to the input - just without the errors.
When something needs fixing, always choose the smallest scope that resolves the problem:
If you find yourself at level 4 or 5, pause and ask: is this actually broken, or just not how I would have phrased it? If the latter - leave it.
If a sentence or section is flagged as incomplete or trails off:
If the user pushes back on a change: accept it immediately, apply it, re-output the full text. No justification, no defensiveness.
| Situation | Action |
|---|---|
| "a average 400 kcal" | Fix to "an average 400 kcal" - wrong article |
| "iffy as fuck" | Preserve - intentional register |
| Sentence ends abruptly mid-thought | Flag, offer completions |
| Long sentence with correct grammar | Leave it - not broken |
| Two words slightly transposed, meaning clear | Fix word order only |
| Comma missing before a conjunction in compound sentence | Add the comma |
| Word repeated twice ("the the") | Remove duplicate |
| Unconventional but readable sentence structure | Leave it |
| Synonym that 'sounds better' | Leave it - not your call |
| Factual claim that seems wrong | Leave it - not a copy edit |
