pprose-copy-edit

name: pprose-copy-edit description: Copy-edit a Markdown document for language and formatting (the Expression and Form dimensions); modifies the doc. A superset of pprose-common-edit. Use when asked to copy edit, proofread, polish, tighten, rewrite, or line edit.

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).

Copy Edit

This is an apply skill: it may modify the target document. It is a superset of pprose-common-edit: it applies the common documentation substrate and the Expression and Form dimensions (E1–E3 and F1–F3: clarity, coherence, concision, organization, consistency, formatting) of the Practical Prose guidelines. It stops short of the substantive dimensions; for a full all-dimension editorial pass that also writes an editorial review, use pprose-full-edit.

Inputs

• Path to one Markdown document.
• Optional edit brief, audience, and tolerance for heavier rewrites.

Steps

1. Run pprose shortcut shortcut-copy-edit and follow it.
2. Apply the common substrate: pprose guidelines common-doc-guidelines.
3. Apply the Expression and Form dimensions (E1–E3, F1–F3) from pprose guidelines practical-prose-guidelines (§Expression Dimensions, §Form Dimensions).
4. If the target is a comprehensive practical guide (a reference work helping readers navigate a complex topic), also read pprose guidelines writing-practical-guides and apply its language-level genre guidance (voice, accessibility, intrigue), honoring each guideline’s applies-when caveat.
5. Audit the document, track issues (project issue/bead tooling when available, else the agent’s to-do/checklist), and apply edits directly.
6. Preserve factual meaning, claim strength, citations, and intentional voice. Do not edit the substantive dimensions (Purpose, Reasoning, Grounding, Judgment); if those need work, note it and recommend pprose-full-edit.
7. Re-scan the diff for regressions before reporting.

Output

Report the changed file, the Expression issue classes fixed, and any substantive (Purpose / Reasoning / Grounding / Judgment) issues you noticed but did not edit.