Clear prose in your editing workflow
Vale brings Google documentation style checks into your editing workflow. Install the plugin in Claude Code or Codex to get automatic checks, an on-demand checking command, and shared writing skills.
Install Vale · Try the examples · Browse the source
Three ways to use Vale
| Need | Use |
|---|---|
| Check edits while you work | Automatic pre-tool, post-tool, and Stop hooks |
| Review selected files | check-prose skill and command |
| Write or improve technical prose | google-prose skill |
Claude Code exposes /vale:check-prose and /vale:google-prose. Codex provides
$vale:check-prose, $vale:google-prose, and the /skills picker. Older Codex clients
that support custom prompts can also use the legacy /prompts:vale template.
Codex 0.158.0 uses the skill interfaces.
One package for both clients
The repository includes marketplaces for Claude Code and Codex. Add
swack-tools/vale-ai-plugin and install vale@vale. Choose Claude Code project
or user scope, Codex's plugin installation, or the manual project and user hook
installers. See the installation guide.
Use one installation method per workspace. Both clients can combine hooks from multiple sources, which can duplicate feedback.
Automatic checks in your editing loop
- Observe. Before the first tool runs, record the workspace file state.
- Check. After tools finish, run Vale on files whose state changed.
- Finish. Before the agent stops, check files touched during the session.
Shell scripts, patches, editors, and MCP tools can all change local files. Vale observes the result without guessing what a shell command does.
A focused checker
The default configuration uses 36 bundled Google rules. It reports warnings and errors and disables spelling checks. Source files use Vale's syntax support to check prose comments. Markdown code blocks remain code.
Vale leaves files unchanged and gives the agent findings to resolve. It checks
an automated subset of the Google style guide and does not format Google Docs.
An existing project .vale.ini takes precedence over the bundled configuration.
Explore the documentation
- Installation: dependencies, marketplaces, scopes, and removal.
- Usage: commands, skills, and examples.
- Marketplaces: distribution, updates, and client compatibility.
- How it works: hook events, file selection, and limits.
- Configuration: style settings and project overrides.
- Troubleshooting: trust, missing tools, and migration.
- Development: tests and the documentation release process.