revise-prose

Sweep repository prose against writing rules and repair violations through dispatched subagents.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill revise-prose-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revise-prose
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/revise-prose
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill revise-prose-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Enforcing a consistent writing style across an entire repository's prose is tedious and error-prone when done by hand. This Skill automates the sweep: it detects rule violations in prose files, dispatches subagents to repair them in batches, and records what has been swept so future runs only cover new or changed rules. ## Core Features & Use Cases - Rule-driven prose sweep: Reads rule units and versions declared by markers in the document, then runs a bundled helper to detect candidates, batch files, and report skipped files by reason. - Batched subagent repair with safety gates: Dispatches up to four prose-reviser subagents per wave, verifies diffs against batch file lists, commits per batch, and pilots the first batch for user approval. - Persistent sweep record: Writes accepted and rejected decisions to .agents/revise-prose.yaml so recorded rejections are re-suppressed and already-swept batches are skipped on later runs. - Use Case: Run a whole-repository sweep to enforce plain-speech and writing-preference rules across all Markdown docs, review questionable repairs in a grouped table, and commit each batch separately. ## Quick Start Ask the agent to revise the prose in this repository against the writing rules, optionally narrowing the sweep to specific paths or using --dry-run for a report only.

Frequently Asked Questions about revise-prose

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

FAQPage Schema
How do I enforce writing style rules across a repository?

Run the revise-prose sweep over the repository to detect violations of the declared writing rules, then let dispatched subagents repair each batch of files. Each batch is committed separately, and a record of swept rules is written to .agents/revise-prose.yaml.

How do I preview prose changes before applying them?

Use the --dry-run flag to produce only a report of candidate violations, with one table per file showing the rule, line, and phrase. A dry run dispatches no subagents, edits nothing, and writes no record.

What is the difference between revise-prose and revise-comments?

revise-comments decides whether a comment exists and what it may say, while revise-prose only adjusts how prose reads and never adds, deletes, or shortens comments. When both apply to the same files, run revise-comments first.

Why does the sweep stop when the git tree is dirty?

An apply run requires a clean tree because the wave gate reads git diff --name-only to verify that only batch files changed. Pre-existing edits would either trip that gate or be committed under the sweep's message, so the run stops and reports the dirty state.

What happens to rejected repairs on the next sweep?

Rejections under versioned rules are recorded in .agents/revise-prose.yaml with rule, file, phrase, and ground. On later sweeps the helper re-supplies them to each batch covering those files, so the same sites are not re-flagged.