I’ve built six spell-checking plugins in under three weeks. This is not an unhealthy interest in spelling. The cost of rolling tools out is the cost of tokens + my time supervising AI. So, before adding another language runtime, package manager, configuration file, and CI job to your project, consider spending an hour vibe coding the missing plugin.
This blog used to run a Python spell checker that took more than three minutes. It’s a Jekyll blog, which is Ruby. Why was I maintaining a Python environment to tell me that I misspelled “hello”? I replaced it with a RuboCop plugin. Spelling became another cop, with the same configuration, exclusions, command, and CI integration as the rest of the checks.
A Rust project shouldn’t need my Ruby setup to check its comments. A JavaScript project that already runs Prettier shouldn’t need an additional Markdown linter just to check spelling.
You can either keep assembling a Frankenstein collection of tools, roll out a custom script, or you can ask AI to build the missing feature.
AI loves simplicity and consistent patterns. This approach pays forward.
Here’s my recent zoo of spell-checking plugins.
- rubocop-spellcheck adds spelling to RuboCop for Ruby comments, strings, identifiers, Markdown, RDoc, AsciiDoc, and plain text. This is a very capable plugin with support for dictionaries and auto-correct.
- dylint-spellcheck adds spelling to Dylint for Rust comments, Rustdoc attributes, Markdown, and plain text.
- markdownlint-rule-spellcheck adds spelling to the Markdown linter you might already be running.
- prettier-plugin-spellcheck adds spelling to Prettier for Markdown, HTML, plain text, JavaScript and TypeScript prose.
- @dblock/oxlint-plugin-spellcheck adds native spelling diagnostics to Oxlint for JavaScript and TypeScript comments, JSX text, and human-facing attributes, with opt-in strings and identifiers.
- eslint-plugin-prose-spellcheck adds offline spelling checks to ESLint’s native Markdown support through
@eslint/markdown. It checks prose, headings, visible link labels, and image descriptions, using CSpell dictionaries and reviewed project vocabulary.
Everything builds on top of simple platforms. The Prettier version is a good example. Prettier already parses Markdown, HTML, JavaScript, and TypeScript. I used its syntax trees to distinguish prose from program structure instead of inventing another parser. Comments and visible text are reasonable things to spellcheck, too.
Install the released plugin:
npm install --save-dev prettier prettier-plugin-spellcheck@0.1.0
Run it without a Prettier configuration:
printf '# helo\n' | npx prettier --plugin prettier-plugin-spellcheck --no-config --stdin-filepath example.md
[error] example.md: Spelling check failed.
[error] example.md:1:3 Misspelled word: "helo". Suggestions: hello, helio, halo.
It’s just another plugin in your existing Prettier setup.
A word of caution when working on new plugins. Initially, Copilot built prettier-plugin-spellcheck as a wrapper on top of markdownlint-rule-spellcheck. Be careful out there.
