proof

Proofread and conservatively edit prose files for spelling, grammar, and consistency.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill proof-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proof
Source: https://github.com/kieranpotts/skills/tree/main/skills/proof
Command: npx skills add https://github.com/kieranpotts/skills --skill proof-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about proof

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I proofread Markdown documentation with an AI agent?▼

Invoke the proof skill with a file, glob, or directory, or let it default to prose files changed in the git working tree. It edits spelling, grammar, and punctuation in place while leaving code blocks, links, and markup untouched.

What file formats does the proof skill support?▼

It supports Markdown, AsciiDoc, reStructuredText, and plain text, selected by extensions like .md, .adoc, .rst, and .txt, plus extensionless prose files such as README and CHANGELOG. Code, configuration, lockfiles, and data files are excluded.

Can the proof skill rewrite or restructure my document?▼

No. It only makes word-level copy edits and never adds, removes, reorders, or splits sections, paragraphs, or list items. Anything that would amount to a rewrite is flagged in the summary for the author instead.

Does the proof skill change code samples or technical facts?▼

No. Code blocks, inline code, commands, identifiers, version numbers, and technical facts stay verbatim. Suspected factual errors are reported in the summary rather than corrected.

What happens when no target files are given to the proof skill?▼

It defaults to the prose files changed in the version control working tree using git status. If the working tree is clean and no files are named, it stops with an error rather than prompting for input.