Back to catalog
proselint
BSD-3-Clauseproselint is an open-source command-line prose linter that replaces Hemingway Editor with fast, offline style checks in Git hooks and CI pipelines.
Open-source alternative to — compare it against:
Overview
Cognitive scientist Jordan Suchow and data scientist Michael Pacer created proselint at UC Berkeley to turn inert writing handbooks into an executable command-line linter. Instead of expecting authors to memorize usage manuals, they translated stylistic advice from editors and classic authors into deterministic rules. Today, that origin gives developers a lightweight, headless style checker that runs offline inside text editors, scripts, and automated test suites.
Why proselint instead of Hemingway Editor
Hemingway Editor focuses on manual, visual editing within a web or desktop application, highlighting dense sentences, passive voice, and adverbs to compute an overall readability grade. That design works well for a solo writer reviewing a single essay, but it introduces friction into technical workflows. Developers cannot easily wire Hemingway Editor into a continuous integration pipeline, run it across hundreds of documentation files at once, or parse its feedback inside terminal buffers.
proselint approaches prose through the lens of performance and automation. As a command-line utility and Python module, it evaluates Markdown, plain text, and documentation files locally on disk without sending content to third-party servers. Documentation teams avoid the latency of browser interfaces and cloud calls; a pre-commit check or CI job evaluates updated articles in fractions of a second. While proselint lacks Hemingway Editor's graphical interface and composite readability score, its ability to output structured diagnostics directly to stdout or JSON makes style validation a repeatable, automated step in the software release process.
What it does well
- Executes locally in milliseconds with zero network calls, keeping private documentation and proprietary comments entirely on developer workstations.
- Emits structured machine-readable diagnostics with file paths, line and column numbers, and suggested replacements when passed
--output-format json. - Supports granular check selection in
proselint.json, enabling teams to toggle individual rules or configure path-based overrides for specific documentation subdirectories. - Integrates into continuous integration workflows and pre-commit frameworks, failing pull requests when contributors commit forbidden corporate jargon or unexpanded acronyms.
