mcpField
C
cw-line-edit

cw-line-edit

github.com/everyincCreative & media377219 installsUpdated 6w ago
Repository

About cw-line-edit

A writing skill for sentence- and word-level revision, intended for writers polishing drafts after developmental editing or working on an existing draft. It combines voice alignment with checks for clarity, style, AI patterns, and factual provenance.

Key features

  1. 01Sentence-level mechanics review
  2. 02Checks for clichés and filler
  3. 03AI-pattern review
  4. 04Writer and project voice alignment
  5. 05Preserves claims and citations
  6. 06Revised draft and change summary

Use cases

  1. 01Polishing a draft after developmental editing
  2. 02Reviewing a draft written elsewhere
  3. 03Checking prose against a project voice
  4. 04Flagging unsupported claims

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/everyinc/compound-writing --skill cw-line-edit

After installing, type/cw-line-editin Claude Code to confirm it loaded.

Details

From the project README

Line Edit

Purpose

A deep, rigorous pass for sentence- and word-level issues. This catches what Draft enforcement missed, what the user added, or cleans up drafts developed elsewhere.

Read ../../references/context-contract.md and load the relevant writer, project, publication, and platform voice sources before editing.

Entry Points

This skill can be invoked:

  1. After completing a developmental edit
  2. Directly by the user with any draft

What to Check

Apply a thorough review for:

Sentence Mechanics
  • Vary sentence length
  • Active voice (flag passive constructions)
  • Concrete nouns and verbs
  • Front-load sentences with important information
Things to Avoid
  • Hedge words ("perhaps," "maybe," "somewhat," "might")
  • Correlatives and negative parallelisms ("not X, but Y")
  • Throat-clearing (delayed starts, excessive setup)
  • Echo statements (saying the same thing multiple ways)
  • Weasel words ("some people say," "studies show" without citation)
  • Empty intensifiers ("very," "really," "extremely")
  • Cliché metaphors
  • Hyperbolic or overblown claims
  • Inflated language
  • Technical, business, or academic jargon
AI Tells

Run cw-ai-check in its required order. When source material or earlier human drafts are available, scan for structural overcompletion before running the full lexicon. Flag and fix:

  • Stock openers ("In today's fast-paced world...")
  • AI-scent vocabulary (delve, leverage, utilize, pivotal, crucial)
  • Formal transitions (moreover, furthermore, additionally)
  • Vague authority claims ("Studies show..." without citation)
  • Formulaic closers ("In conclusion...")
  • Structural patterns ("No X. No Y. Just Z.")
  • All patterns in the ai-check lexicon
Voice Alignment

Check the prose against the active writer and project voice sources. Do not make a sentence cleaner by erasing intent, humor, rhythm, priors, or a distinctive aside.

Meaning And Provenance
  • Preserve the scope and certainty of factual claims.
  • Do not sever citations or source attribution from the claims they support.
  • Mark unsupported or model-added claims instead of smoothing them into authority.

Output

Part 1: Revised Draft

Deliver the full draft with all fixes applied. Present it ready-to-use.

Part 2: Summary of Changes

After the revised draft, summarize material changes in order of appearance. Do not bury the usable copy beneath a diagnostic preamble.

---

## Changes Made

1. **Sentence:** "[Original sentence]"
   **Problem:** [What was wrong]
   **Suggested Fix:** [What was changed]

2. **Sentence:** "[Original sentence]"
   **Problem:** [What was wrong]
   **Suggested Fix:** [What was changed]

[Continue for all changes...]

Reverting Changes

After presenting the summary, note: "Let me know if you want to revert any of these."

Writer can revert by:

  • Number: "Revert #3 and #7"
  • Natural language: "Put back the original for the one about hedging"

System handles either format.

Transition

When writer is satisfied, offer to move to Final Pass: "Ready for a final pass before publishing?"

Lessons

[Skill-specific lessons will be added here as they're captured]

Comments

Markdown supported