Apply the common Markdown documentation guidelines to any document; modifies the doc. The basic, universal edit tier. Use when asked to tidy, clean up, conform, fix formatting/structure, or add the footer.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Apply the common Markdown documentation guidelines to any document; modifies the doc. The basic, universal edit tier. Use when asked to tidy, clean up, conform, fix formatting/structure, or add the footer.
Run pprose as pprose <command> if on PATH, else uvx pprose@0.2.0 <command>
(zero-install via uv).
Run pprose --help for every command, pprose skill for the other Practical Prose
skills, and pprose list for all on-demand playbooks, style guides, and procedures
(pprose shortcut, pprose guidelines, pprose runbook each print one by name).
Common Edit
This is the basic, universal edit tier (an apply skill: it may modify the target
document). It applies only the common documentation guidelines (read them with
pprose guidelines common-doc-guidelines) — organization, structure, writing style,
Markdown formatting, links, headings, lists, frontmatter, and footer — so it is safe for
almost any Markdown document, workflow, or repo, whether or not it is a Practical Prose
artifact.
For a deeper language-and-formatting pass (the Expression and Form dimensions) use
pprose-copy-edit; for a full all-dimension editorial pass use pprose-full-edit. Each
tier is a superset of the one before.
Inputs
Path to one Markdown document.
Optional scope note from the user, such as “format only” or “make all obvious fixes.”
Steps
Run pprose guidelines common-doc-guidelines and read it.
Inspect the target against organization, structure, writing style, Markdown
formatting, links, headings, lists, frontmatter, and footer rules.
Apply fixes directly to the document while preserving its intended content and voice.
Ensure the required guideline footer is present when the document is part of this
repo’s durable documentation.
Re-read the diff and check that no edit changed factual meaning.
Output
Report the changed file, the main issue classes fixed, and any rule you intentionally
left alone.