Your style.
Our editor.
Vale brings code-like linting to prose. Turn a team’s style guide, a house voice, or a journal’s author guidelines into checks that run in your editor and alongside your code.
brew install vale macOS, Windows & Linux · Runs offline · Other installs
Writing guide · Terminology
The product is Vale CLI. Don’t write Vale cli or vale-cli.
styles/Docs/Terms.yml
docs/install.md
- # Installation
- Vale cli runs on macOS, Windows, and Linux.
Thanks to Claude for Open Source.
Watch
Vale in a minute.
0:03 Your guideline 0:10 A rule you own 0:17 Published styles 0:23 A run 0:29 The fix 0:36 What Vale sees 0:45 Wherever you write 0:52 Tested and fast 1:00 Install
Supporting the project
Sponsor spotlights
These companies support Vale's future — and put it to work in their own products today.
Used in production
Read their configs
Every team here publishes something you can open — the .vale.ini they run,
or the page they wrote about running it. Hover a mark for where.
- Datadog 20,000 docs pull requests merged in 2023 From 1,400 contributors, with an on-call writer reviewing over 40 a day. Vale runs before they look. Read the source
- GitLab 69 Vale rules in the docs pipeline Two styles, gitlab_base and gitlab_docs, run on every merge request; error-level rules fail the job. Read the source
- Grafana Labs 106 style-guide rules, as Vale checks The Writers' Toolkit lists every rule by name, from em dashes to "please", each with the fix. Read the source
- Red Hat 37 rules in the RedHat style Language rules for open source docs, mandatory for Red Hat products, and published as a package anyone can sync. Read the source
Why Vale
Most tools see text. Vale sees a document.
Check the writing in context. Target a heading, a comment, or a description, while leaving the code around it alone.
- 01 Scopes Parses your markup instead of guessing at it. Read more
- 02 Code Your comments are documentation too. Read more
- 03 Views Prose inside files that aren’t prose. Read more
- 04 Speed One binary, nothing to install alongside it. Read more
- The same answer on every run.
- A rule’s verdict is decided before the draft exists. Test each one against the sentences it should catch and the ones it should leave alone. Testing rules
- Milliseconds, not tokens.
- On one draft, Vale and a model review found the same fourteen long sentences. Vale took 70 milliseconds; the review took 46 seconds and 45,000 tokens. Read the measurements
- Yours to read.
- Rules are YAML files in your repository, reviewed in a pull request like any other change. Vale runs offline, so no draft leaves your machine.
- A model writes the rule. The rule checks the docs.
- Describe a guideline in a sentence and your agent writes the YAML and its tests. Its attention then goes to what no pattern can judge. Agent skills
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.
- Apps Wherever the prose gets written, with diagnostics as you type.
- Automation The same run, before anything merges.
- Documentation platforms Hosted docs that run Vale for you.
Vale for your browser
Your style guide, in every text box.
The extension checks what you write on the web, from a pull-request description to an email, against your Vale configuration.
- Marks as you type, in text areas, inputs, and rich editors, on the sites you turn on.
- A card on each mark with its fix, from a click or Alt+Enter.
- One configuration everywhere: library packages, or your house style as a .zip.
- Free, with no account. Vale runs inside the extension, so nothing leaves your browser.
- Chrome Soon
- Edge Soon
- Firefox Soon
Source on GitHub Privacy policy Thanks to FLOSS/fund for funding it.
Vale for agents
Your assistant writes the docs. Something should check them.
A model writes plausible prose with confidence either way. Vale tells it which sentences break your style, in the turn it wrote them.
- Skills Free One-prompt onboarding, style choices, rules from your style guide, fixes, CI, and commit messages, each run through the CLI in your repository.
- Hooks Free Lint each file the assistant writes and each commit it makes, and hand the alerts back in the same turn.
- MCP server Vale CMS The engine as tools, so a rule the assistant writes is compiled and tested before you see it.
A few lines of config.
A consistent first draft.
Start with an existing style guide. Keep the configuration in your project so everyone runs the same checks.
- Install Vale.
brew install valeon macOS and Linux,choco install valeon Windows, or another package. - Pick your styles.Save this as
.vale.iniin your project. - Sync, then lint.Download the styles and check your docs.
Working with a coding assistant? Agent tools has it do all three, then lint every file it writes.
Or have your assistant set it up
/plugin marketplace add vale-cli/agent-tools /plugin install vale@agent-tools
Type both in Claude Code, then run /vale:onboard. It shows one proposal and
writes nothing until you say yes.