mechanical-preprocess

Runs a bash preprocessing pipeline to standardize punctuation and remove repetitive phrasing across manuscript chapters.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/PhilipStark/book-genesis --skill mechanical-preprocess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mechanical-preprocess
Source: https://github.com/PhilipStark/book-genesis/tree/main/skills/mechanical-preprocess
Command: npx skills add https://github.com/PhilipStark/book-genesis --skill mechanical-preprocess

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill handles mechanical cleanup of manuscript text at scale, addressing em-dash usage, forbidden words, and repetitive structures before AI agents touch the text. It uses a bash-first approach to perform safe, deterministic transformations while preserving voice and enabling later AI review.

Core Features & Use Cases

  • Bash-first cleanup: pattern matching, counting, and safe replacements across chapters.
  • Phase-based workflow: scan, replace, AI-quality-review, and reporting with diffs.
  • Output & traceability: generates diffs per chapter and a final mechanical-preprocess-report to guide manual review.
  • Use Case: Run this before dialogue polishing to reduce mechanical noise across 30+ chapters.

Quick Start

Run the mechanical-preprocess workflow on your chapters directory to clean em-dashes, forbidden words, and repetition before AI editing.

Frequently Asked Questions about mechanical-preprocess

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

FAQPage Schema
How do I standardize em-dashes and remove forbidden words across a multi-chapter manuscript?

Standardize em-dashes and remove forbidden words across a multi-chapter manuscript by running a bash-driven preprocessing pipeline that performs deterministic pattern matching and safe text replacements before any AI editing.

What is the best way to clean up repetitive phrasing in manuscript text before AI editing?

Cleaning up repetitive phrasing before AI editing is best handled by a mechanical preprocessing workflow that scans chapters, applies safe replacements, and generates a review report with diffs to preserve the author's voice.

Can I use bash scripts for mechanical manuscript cleanup on 30 or more chapters?

Yes, you can use bash scripts for mechanical manuscript cleanup on 30 or more chapters, as the workflow uses bash-first pattern matching and counting to apply safe deterministic transformations across large multi-chapter files.

How does a phase-based mechanical cleanup workflow handle manuscript text processing?

A phase-based mechanical cleanup workflow handles manuscript text processing through four distinct stages: scanning the text, replacing target patterns, reviewing quality, and reporting with per-chapter diffs and a final summary report.

When should I run mechanical text cleanup in my manuscript editing workflow?

You should run mechanical text cleanup at the beginning of your manuscript editing workflow, specifically before AI agents touch the text, to reduce mechanical noise and ensure standardized punctuation for later dialogue polishing.

Does mechanical manuscript preprocessing preserve my original writing voice?

Mechanical manuscript preprocessing preserves your original writing voice by using deterministic bash-driven transformations for punctuation and repetitive structures, which provides safe replacements and outputs diffs for manual review rather than altering style.