Humanizer Pipeline Open-Sourced: Six-Step Markdown File for AI Text Post-Processing

A Reddit user has open-sourced a humanizer pipeline that runs as a single Markdown file with a six-step process for post-processing AI-generated text. The repo at github.com/milock/humanizer contains the pipeline, which prioritizes surgical patching over full rewrites unless severity thresholds are crossed.

Pipeline Steps

• Channel auto-detection: Detects email, Slack, LinkedIn, blog post, case study, landing page, or meeting agenda from cues like greetings, hashtags, code fences, word count, and voice signals. Each channel applies different rules.
• Voice calibration (optional): Accepts a voice profile file or a writing sample to derive a six-line profile. Skipped by default.
• Pattern scan: Scans in fixed order — 16 named structural patterns (dramatic reframe, manufactured punchline, runway sentence, performative directness, dramatic fragment Q&A, anaphora, copula avoidance, etc.), then vocabulary in three tiers (always-replace, cluster-flag, density-flag), then checks for point of view and concrete detail, then punctuation budgets and banned openers.
• Severity gate: If hits exceed thresholds (5+ vocab hits, 3+ pattern categories, uniform sentence length), the pipeline throws out the draft and rewrites from the outline. Otherwise it patches surgically.
• Rewrite: At the chosen depth, preserving voice.
• Self-audit pass: Asks “what makes the rewrite still obviously AI generated?” and revises again.

Key Design Decisions

• Channel-aware strictness: Short Slack messages are scrutinized less than landing page headlines. Sentence fragments are fine in Slack but flagged in long-form. One-line paragraphs are normal on LinkedIn.
• [HOLLOW] flag: Marks drafts that pass AI detection but say nothing specific — a separate problem from “reads like AI.”
• Voice profile schema: Declare intentional patterns (e.g., fragments and “And/But” sentence starts) so the pipeline leaves them alone.
• Setup mode: A 7-question interview populates a voice profile if you don't have one.

Output Format

The pipeline produces a structured report with stable section headers: Issues Found, Rewritten Draft, What Changed, Self-Audit, Final Version, Humanizer Report. This is parseable for chaining after a writer agent.