Vale is a linter for prose
A command-line tool that brings code-like linting to your writing. Enforce a consistent editorial style across every doc, in any format—entirely offline.
Thanks to Claude for Open Source.
Read their configs
Every team here publishes something you can open — the .vale.ini they run, or the page they wrote about running it.
-
The EKS User Guide walks contributors through installing Vale for live style feedback.
docs.aws.amazon.com Cloud & infrastructure -
Runs a packaged PowerShell-Docs style in their Documentarian toolkit.
microsoft/Documentarian github.com - Discord
Vale's built-in rules across the public API documentation.
.vale.ini discord/discord-api-docs -
A required check in GitLab's documentation testing pipeline.
docs.gitlab.com Developer tools -
Powers the prose linting rules in the Grafana Writers' Toolkit.
grafana.com Data & observability - NVIDIA
All NeMo Agent Toolkit documentation is checked with Vale before it merges.
docs.nvidia.com Developer tools -
Enforces style standards across the Docker product docs.
.vale.ini docker/docs -
Maintains "Vale at Red Hat", a public style package and onboarding guide.
redhat-documentation.github.io Open source -
Publishes datadog-vale and shifted docs quality left with it.
datadoghq.com Data & observability
Why Vale
Most tools see text. Vale sees a document.
A heading, a code block, a comment, and a link URL are not the same thing—and a rule that can't tell them apart is a rule you end up switching off.
Parses your markup instead of guessing at it
Markdown, AsciiDoc, reStructuredText, MDX, MyST, Quarto, Typst, HTML, XML, DITA, Org, and QDoc each go through a real parser. Rules can target headings, lists, or table cells—and code spans, URLs, and fenced blocks are skipped before a rule ever runs.
How scopes workYour comments are documentation too
Vale lifts comments out of more than twenty languages with tree-sitter grammars, so it knows where a comment ends and a marker inside a string literal stays code. The Markdown inside a doc comment is linted as though it were its own file.
Inside the grammarRules are YAML—no plugin API, no compile step
Twelve extension points, from banned terms to readability scores to part-of-speech patterns. Write one in a text editor, drop it in a folder, and share the folder as a package.
All twelve extension pointsOne binary, nothing to install alongside it
Written in Go, with no runtime and files linted in parallel. GitLab runs 82 rules across all 2,827 pages of its documentation in under twenty seconds.
What makes it fast- 2,827
- pages of Markdown
- 82
- rules applied
- <20s
- start to finish
Private by design
Nothing leaves your machine. No account, no upload, and no training on your writing.
Runs everywhere
macOS, Windows, and Linux. MIT-licensed and maintained in the open.
Style guides included
Microsoft, Google, Red Hat and thirteen more, each installed with one command.
Distribution
Where Vale is downloaded
- GitHub Releases0 downloads · lifetime
- Docker Hub0 downloads · lifetime
- PyPI0 downloads · past 6 mo · community-maintained wrapper
- conda-forge0 downloads · lifetime
- Homebrew0 downloads · past 12 mo
- Chocolatey0 downloads · lifetime
Sources: GitHub, Docker Hub, PyPI, conda-forge, Homebrew, Chocolatey, winstall, Snapcraft, and Repology · 61 contributors · updated 2026-07-24
One tool, every app
More than just a command-line interface.
Vale runs where you already write—in your editor, in your notes app, and in CI before anything merges.
Editors
Through the language server, so diagnostics arrive as you type.
Writing apps
The same rules, away from the editor.
Automation
The same run, before anything merges.
Documentation platforms
Hosted docs that run Vale for you.