vale

Lint Markdown and documentation for style and spelling issues.

1|2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alunduil/alunduil-chezmoi --skill vale-alunduil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vale
Source: https://github.com/alunduil/alunduil-chezmoi/tree/main/dot_claude/skills/vale
Command: npx skills add https://github.com/alunduil/alunduil-chezmoi --skill vale-alunduil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vale reduces friction in maintaining consistent prose across a project by automatically linting, flagging style and spelling issues, and providing vocab guidance so teams ship clearer docs.

Core Features & Use Cases

  • Configurable styles and per-format rules via StylesPath, Packages, and Vocab.
  • CI-ready linting for Markdown, README, and documentation to catch style and spelling issues.
  • Vocab customization via accept/reject lists to enforce project terminology.

Quick Start

Run Vale on your Markdown files to surface style and spelling issues and integrate with pre-commit checks.

Frequently Asked Questions about vale

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lint Markdown documentation to catch spelling and style issues?

You can lint Markdown documentation by running Vale with a configured StylesPath, Packages, and MinAlertLevel to automatically surface and flag spelling, formatting, and style issues across your repository files.

What is the best way to enforce consistent project terminology in technical docs?

To enforce consistent project terminology in technical docs, configure Vale Vocab with an accept.txt file, allowing your team to define specific project terms and automatically flag spelling deviations from approved vocabulary.

Can I use Vale to audit documentation formatting in a CI pipeline?

Yes, you can use Vale to audit documentation formatting in a CI pipeline by integrating it with your repository checks to automatically lint Markdown and README files for style and spelling issues.

How do I configure per-format rules for README and Markdown files?

You configure per-format rules by defining BasedOnStyles in your Vale configuration file, allowing you to apply specific style guidelines and formatting checks to distinct formats like Markdown and README files.

Do I need a Vale configuration file to start checking repository prose?

Yes, you need a Vale configuration file containing StylesPath, Packages, and MinAlertLevel settings to define your style rules and vocabulary before you can start checking repository prose.

Why does Vale flag correctly spelled project terms during a documentation audit?

Vale flags correctly spelled project terms during a documentation audit because they are missing from your Vocab accept.txt list, causing the linter to treat unrecognized project terminology as spelling errors.