Run pprose as pprose <command> if on PATH, else uvx pprose@0.1.0 <command>
(zero-install via uv).
Run pprose --help for every command, pprose skill --list for the other Practical
Prose skills, and pprose shortcut --list / pprose guidelines --list /
pprose runbook --list for on-demand playbooks, style guides, and procedures.
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
- Run
pprose shortcut shortcut-copy-edit and follow it.
- Apply the common substrate:
pprose guidelines common-doc-guidelines.
- Apply the Expression and Form dimensions (E1–E3, F1–F3) from
pprose guidelines practical-prose-guidelines (§Expression Dimensions, §Form
Dimensions).
- Audit the document, track issues (project issue/bead tooling when available, else the
agent’s to-do/checklist), and apply edits directly.
- 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.
- 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.
1---2name: pprose-copy-edit-23description: 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.4---5<!-- DO NOT EDIT: generated by `pprose install` (format=f01) -->67> Run pprose as `pprose <command>` if on PATH, else `uvx pprose@0.1.0 <command>`8> (zero-install via uv).9> Run `pprose --help` for every command, `pprose skill --list` for the other Practical10> Prose skills, and `pprose shortcut --list` / `pprose guidelines --list` /11> `pprose runbook --list` for on-demand playbooks, style guides, and procedures.1213# Copy Edit1415This is an apply skill: it may modify the target document.16It is a **superset of `pprose-common-edit`**: it applies the common documentation17substrate *and* the Expression and Form dimensions (E1–E3 and F1–F3: clarity, coherence,18concision, organization, consistency, formatting) of the Practical Prose guidelines.19It stops short of the substantive dimensions — for a full all-dimension editorial pass20that also writes an editorial review, use `pprose-full-edit`.2122## Inputs2324- Path to one Markdown document.25- Optional edit brief, audience, and tolerance for heavier rewrites.2627## Steps28291. Run `pprose shortcut shortcut-copy-edit` and follow it.302. Apply the common substrate: `pprose guidelines common-doc-guidelines`.313. Apply the Expression and Form dimensions (E1–E3, F1–F3) from32 `pprose guidelines practical-prose-guidelines` (§Expression Dimensions, §Form33 Dimensions).344. Audit the document, track issues (project issue/bead tooling when available, else the35 agent’s to-do/checklist), and apply edits directly.365. Preserve factual meaning, claim strength, citations, and intentional voice.37 Do not edit the substantive dimensions (Purpose, Reasoning, Grounding, Judgment); if38 those need work, note it and recommend `pprose-full-edit`.396. Re-scan the diff for regressions before reporting.4041## Output4243Report the changed file, the Expression issue classes fixed, and any substantive44(Purpose / Reasoning / Grounding / Judgment) issues you noticed but did not edit.
jlevy