prose-editor

Reviews prose and markdown documents with atomic suggestion cards and verbatim quote validation.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill prose-editor-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prose-editor
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/prose-editor
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill prose-editor-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing prose with git diffs on soft-wrapped paragraphs creates visual noise and makes review painful. This Skill delivers structured, granular editing feedback as atomic suggestion cards, each with a verbatim original quote, proposed revision, and rationale, without ever modifying source files. ## Core Features & Use Cases - Atomic Suggestion Cards: Every edit is isolated into a card with anchor, exact original quote, proposed revision, optional diff block, and terse rationale, validated against a JSON schema. - Three Editing Tiers: Choose proofread (mechanics only), line edit (sentence-level craft, default), or developmental (macro structure) depending on your goals. - Verbatim Fidelity Validation: A bundled Python validator parses cards, enforces schema enums and unique IDs, and confirms every original quote exists exactly once in the source document. - Use Case: Run a structured review on a 5,000-word technical design doc. The Skill chunks it by headings, emits sequentially numbered suggestion cards per section, and you validate the output with the bundled CLI before applying any edits. ## Quick Start Ask the assistant to run a line-edit review of your markdown file, for example: review docs/architecture.md with the prose editor and show suggestion cards.

Frequently Asked Questions about prose-editor

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

FAQPage Schema
How do I review a markdown document for grammar and clarity?

Invoke the prose editor on the file path to receive atomic suggestion cards, each containing an anchor, verbatim original quote, proposed revision, and rationale. Choose the proofread tier for mechanics only or line edit for sentence-level craft.

How do I review only changed prose files in a git diff?

Use the diff mode flag to restrict review to modified prose files in the active changeset. Only .md, .markdown, .rst, .txt, .tex, and .adoc files are parsed; code, config, and binary files are automatically skipped.

Does the prose editor modify my source files automatically?

No, the editor operates in advisory-only mode and never modifies source files during a review pass. It outputs suggestion cards that you review and apply manually at your discretion.

How do I validate that suggestion cards match the source text?

Run the bundled validator.py CLI with the review file and a --source flag pointing to the original document. It parses cards, checks schema enums and unique IDs, and confirms every original quote appears verbatim exactly once in the source.

What happens when reviewing documents larger than 3000 words?

Large documents are split into logical chunks by top-level markdown headings and processed section by section. Suggestion card IDs remain globally sequential across all chunks to prevent duplication and context drift.

Why does card validation fail with a verbatim quote mismatch?

Validation fails when the Original field does not match the source text byte-for-byte or appears multiple times ambiguously. Quote the exact substring and include surrounding anchor context to make it unique.