line-editing
This skill should be used when the user asks to "line edit", "edit my prose", "polish this chapter", "tighten the prose", "improve the sentences", "copyedit", "proofread", "proof pass", "check grammar and punctuation", "dialogue punctuation", "make the voices distinct", "everyone sounds the same", "read it aloud", "read-aloud pass", "text to speech", or wants a sentence-level quality pass on drafted chapters that preserves the author's voice. NOT for creating the style sheet or checking voice consistency (use voice-style).
danjdewhurst · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add danjdewhurst/story-skills --skill line-editing技能说明
name: line-editing description: This skill should be used when the user asks to "line edit", "edit my prose", "polish this chapter", "tighten the prose", "improve the sentences", "copyedit", "proofread", "proof pass", "check grammar and punctuation", "dialogue punctuation", "make the voices distinct", "everyone sounds the same", "read it aloud", "read-aloud pass", "text to speech", or wants a sentence-level quality pass on drafted chapters that preserves the author's voice. NOT for creating the style sheet or checking voice consistency (use voice-style).
Line Editing
Overview
Own the prose-quality passes that come after structure is settled: the
line edit (sentence clarity, rhythm, precision, voice), character-voice
differentiation, the copyedit against style-sheet.md, a read-aloud pass,
and a proof pass on a built copy. Every change is proposed with a
before/after and a one-line rationale so the author can accept or reject
it. The author's voice is the standard, not the agent's taste. The
better-writing skill, when installed, is an optional complement for
anti-generic checks; this skill does not depend on it.
Prerequisites
A story project with story.md and drafted chapters (status draft or
later). Read style-sheet.md if present; if it is missing or thin, build
it first with the voice-style skill, because the copyedit checks against
it.
Language
Read language in story.md (a BCP 47 tag such as en-GB, fr, or
ja; a missing field means en). Edit in that language and to its
grammar and conventions, and write edit notes in the language the user
works in with you, quoting the prose exactly as written. The checklists'
word-level advice (filter words, -ly adverbs, said, dialogue
punctuation) is English: for another language, apply its aim, not its
word lists, and take dialogue and punctuation from the style sheet and
references/language-conventions.md. When story prose or
story voices reports a check skipped for the book's language, or a
check plainly does not fit it, do that pass by reading.
When to Use
- A chapter's structure is settled and the prose needs polish
- Dialogue sounds the same from every speaker
- Preparing a manuscript for beta readers, an editor, or submission
- The
line,copyedit, orproofrevision pass is next instory passes - NOT for structural, plot, or continuity revision (use
revision-continuity; line-edit only after those passes, or the polish is wasted) - NOT for setting house style or the voice description (use
voice-style; this skill applies it) - NOT for scene-level craft such as deep POV, subtext, or exposition strategy (use
scene-craft) - NOT for acting on external reader notes (use
feedback-triage) - NOT for writing or scanning verse (use
verse-craft); this skill only flags rhymes that slipped into prose by accident
Workflow
1. Scope and permission
- Ask which chapters and which pass: line edit, voice differentiation, copyedit, read-aloud, or proof. Default order is the one below.
- Ask how heavy the edit should be: light (errors and clear improvements only), medium (tighten and clarify), or heavy (restructure sentences and paragraphs). Default to light.
- Never rewrite a passage wholesale without explicit permission. Propose edits; apply only what the author accepts, or apply all on explicit instruction.
- Snapshot before a multi-chapter pass (see Draft Snapshots in the
revision-continuityskill), and mark the pass in progress. Ifstory.mdhas norevision-passesyet,story passes . --initwrites the default ladder first;story passes .shows where the book is.
story passes . --start line
2. Line edit
- Read
story.md(POV, tense, Tone & Style), the style sheet's Voice section, and the chapter. Runstory prose .for the chapter's counts. If the style sheet has nosamples, suggest the author list an earlier book or chapters they are happy with (see thevoice-styleskill), so the counts are measured against their own voice. Aprose-baseline-*warning shows where a chapter drifts from it: use it to find passages to reread, and keep any drift the author meant. - Work paragraph by paragraph with
references/line-edit-checklist.md: clarity, precision, economy, rhythm, POV distance, and voice. - Present edits in the format in
references/edit-note-format.md: location, before, after, and one line of rationale. Group by paragraph; lead with the highest-impact changes; cap a batch at about 20 so the author can review them. - Leave passages that are unusual but deliberate. When unsure whether a quirk is voice or error, ask.
- To check a rewritten passage before putting it in the chapter, pipe it
in:
story prose - < rewrite.mdlints it against the style sheet, andstory voices - < rewrite.mdchecks its dialogue against the characters'voice-avoidlists.
3. Differentiate character voices
story voices .
The report fingerprints each character's attributed dialogue (sentence
length, contractions, questions, exclamations, signature words) and warns
when two voices are near-identical, when a character says a
voice-avoid word, and when a voice-words entry never appears.
- For near-identical pairs, read both characters' Voice & Speech
Patterns sections and propose line-level changes that follow them:
vocabulary, sentence length, what each avoids saying, how each deflects.
See the voice section of
references/line-edit-checklist.md. - If a character file has no voice notes, propose
voice-wordsandvoice-avoidlists drawn from their best existing lines, and ask before adding them to the character file. - A line is attributed only when the narration names the speaker next
to a speech verb or, failing that, names exactly one character in the
paragraph. Pronoun tags (
she said) and untagged lines are invisible