# Pprose Common Edit

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

- Skill: `jlevy/pprose-common-edit-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jlevy/pprose-common-edit-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jlevy/pprose-common-edit-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing, AI & ML
- Author: jlevy (https://skillmd.com/u/jlevy)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/jlevy/pprose-common-edit-2

---

<!-- DO NOT EDIT: generated by `pprose install` (format=f01) -->

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

# 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

1. Run `pprose guidelines common-doc-guidelines` and read it.
2. Inspect the target against organization, structure, writing style, Markdown
   formatting, links, headings, lists, frontmatter, and footer rules.
3. Apply fixes directly to the document while preserving its intended content and voice.
4. Ensure the required guideline footer is present when the document is part of this
   repo’s durable documentation.
5. 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.