edit

Detect and fix spelling, grammar, phrasing, and word echoes in chapters.

14|6|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/howells/fiction --skill edit-howells
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit
Source: https://github.com/howells/fiction/tree/main/skills/edit
Command: npx skills add https://github.com/howells/fiction --skill edit-howells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps writers automatically catch and fix spelling, grammar, and style issues at the line level across chapters.

Core Features & Use Cases

  • Spelling and grammar checks for line-level polish across drafts
  • Detection of awkward phrasing and word echoes to improve readability
  • Parallel processing of multiple chapters to speed up revisions
  • Updates to progress.md with findings and suggested fixes

Quick Start

Run the line-level editor on a single chapter, a range, or all drafted chapters to start polishing.

Frequently Asked Questions about edit

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

FAQPage Schema
How do I automate line-level proofreading for spelling and grammar across multiple manuscript chapters?

Automated line-level proofreading detects and fixes spelling, grammar, phrasing, and word echoes across drafted chapters. You can run it on a single chapter, a range, or all drafted chapters simultaneously using parallel processing to speed up revisions.

Can I check an entire manuscript for awkward phrasing and word echoes in one pass?

Yes, you can process all drafted chapters simultaneously to detect awkward phrasing and word echoes. The tool outputs a per-chapter report alongside a combined manuscript-wide summary, utilizing parallel processing to accelerate large-scale revisions.

How does parallel processing work when editing large manuscripts with many chapters?

Parallel processing speeds up revisions by handling multiple chapters concurrently rather than sequentially. This allows large manuscripts to undergo line-level proofreading for spelling, grammar, and phrasing issues efficiently while generating individual chapter reports and a combined summary.

What is the best way to review suggested grammar and spelling fixes before applying them?

The editor records all findings for review and offers optional automatic fixes. It generates a per-chapter report and a manuscript-wide summary detailing detected spelling, grammar, and phrasing issues, allowing you to evaluate suggested corrections before committing changes.

Does the line editor update progress tracking files automatically after proofreading chapters?

Yes, the line editor requires careful handling to update progress.md with findings and suggested fixes after proofreading. This ensures manuscript revision status and line-level corrections are tracked accurately across individual chapters and the full draft.

When should I use automated line-level editing instead of manual proofreading for my draft?

Automated line-level editing is ideal for large manuscripts needing spelling, grammar, phrasing, and word echo detection across many chapters. It provides parallel processing, optional automatic fixes, and comprehensive reporting that manual proofreading cannot efficiently match at scale.