What problem does it solve? Documentation, READMEs, and release notes often ship with typos, grammar errors, and inconsistent terminology because manual proofreading is tedious and easy to skip. This Skill performs a careful final-pass copy edit on prose files, fixing language issues without touching code, markup, or technical meaning. ## Core Features & Use Cases - Conservative copy editing: Fixes spelling, grammar, punctuation, typos, and awkward phrasing in Markdown, AsciiDoc, reStructuredText, and plain text, while protecting code blocks, links, identifiers, and version numbers. - Consistency enforcement: Standardizes terminology and capitalization across files and follows the project's established variety of English. - Author flagging: Reports issues that would require a rewrite — factual errors, chatbot residue, overused semicolons — instead of silently changing meaning. - Use Case: Before a release, point the Skill at your changed docs and get a clean, reviewable diff of word-level edits plus a per-file summary, with nothing staged or committed. ## Quick Start Proofread the prose files changed in my working tree and fix spelling and grammar in place.