Content and publishing · Edition No. 10 · 4 Sep 2026

vale-cli/vale

A linter for your voice — the difference between a site that sounds like a company and one that sounds like nine separate afternoons.

← Content and publishingRead the whole edition →

6.1k stars · MIT · v3.20.0 (2026-09-02)

A linter for your voice — the difference between a site that sounds like a company and one that sounds like nine separate afternoons.

Repo detailsthe review · specs · pros & cons · install

What it is

A markup-aware command-line linter for prose. You point it at a style — Microsoft's, Google's, or a set of YAML rules you write yourself — and it flags passive voice, banned phrases, heading capitalisation and inconsistent product terms across Markdown, HTML and MDX, while ignoring the code and front-matter around them.

Why it matters

LanguageTool tells you a sentence is wrong. Vale tells you it is not yours. Writing docs, blog posts and video descriptions over months, the failure is not grammar, it is drift: "sub-topic" on Monday and "subtopic" on Friday, "map" in the hero and "graph" in the docs. Those wobbling terms are exactly the strings an AI answer engine would otherwise quote you by, so terminology consistency is an AI-search asset rather than a style hobby — the same argument geo-optimizer-skill (Ed.8 #3) makes about structure, applied to vocabulary. And since Claude Code writes a great deal of your copy, a checked-in rules file is the only way to make it write in your voice rather than a plausible average one.

Stars6.1k
LicenceMIT
Latestv3.20.0 (2026-09-02)checked 7 Sep 2026
Written inGo
NeedsDocker
RunsSelf-hosted on your own server
Setup effort
2 / 5
Payoff
4 / 5
Good
  • MIT, a single binary, no runtime to install — it will still work in three years.
  • Understands Markdown and MDX, so it drops straight into Astro and Starlight (Ed.4 #4) without mangling components.
  • Twenty lines of YAML gives you an enforceable house glossary — the cheapest brand consistency available.
Watch for
  • It ships almost no rules of its own: day one is installing or writing a style package, so the first session is configuration rather than results.
  • Off-the-shelf styles produce false positives on technical writing until tuned, and an ignored linter is worse than none.
  • The repository has moved — errata-ai/vale now redirects to vale-cli/vale. Ownership changes are worth watching on a tool you build a workflow around.
How to get it

A .vale.ini at the repo root, vale docs/ in the Astro build and in a git pre-commit hook.

Get the next edition in your inbox

A dozen repositories, opened and checked. The licence read, the last release dated, and the ones that did not make it named with the reason. It is the half most lists leave out.

No tracking pixels. One click to leave. The archive stays free either way.

We use your address to send the edition and nothing else. Confirm by email, leave in one click. How we handle it.