edit_skill

Overview

This skill runs a line-level editor across chapters to catch mechanical and stylistic problems. It produces chapter reports with flagged lines, suggested fixes, and manuscript-wide patterns. It can apply fixes automatically and records progress for the project.

How this skill works

The skill scans chapters for spelling, grammar, awkward phrasing, word echoes, and formatting inconsistencies. For multiple chapters it spawns parallel editor agents so each chapter is processed concurrently, then aggregates findings into a combined report. Each chapter report lists issues by category and line number and offers suggested fixes; you can choose to apply fixes automatically. The skill also updates a progress record with summary patterns and actions taken.

When to use it

• After finishing a chapter draft
• Before sending chapters to beta readers
• During revision passes focused on clarity and mechanics
• After a story-level review has addressed plot and structure
• When preparing a manuscript for final polish

Best practices

• Run story-level review first to avoid editing around unresolved plot problems
• Edit in ranges or ‘all’ using parallel agents for large projects to save time
• Review aggregated manuscript patterns (overused words, crutch phrases) before global replacements
• Accept automatic fixes selectively—scan suggested changes when nuance matters
• Run continuity checks after mechanical edits to confirm cross-chapter consistency

Example use cases

• /fiction:edit — polish the most recent chapter before sharing with a reader
• /fiction:edit 5 — clean up chapter 5’s grammar, phrasing, and formatting
• /fiction:edit 3-7 — run a batch edit across a draft arc to surface repeated issues
• /fiction:edit all — spawn parallel agents to edit every drafted chapter quickly and compile manuscript-wide trends
• Use the aggregated report to identify and replace a crutch word across the manuscript