#spellcheck #spelling #grammar

bin+lib cargo-spellcheck

Checks all doc comments for spelling mistakes

89 releases

Uses new Rust 2021

0.11.2 Mar 31, 2022
0.10.1 Feb 6, 2022
0.9.6 Dec 15, 2021
0.9.4 Nov 24, 2021
0.3.0 Jul 29, 2020

#77 in Cargo plugins

Download history 90/week @ 2022-01-29 84/week @ 2022-02-05 107/week @ 2022-02-12 191/week @ 2022-02-19 60/week @ 2022-02-26 68/week @ 2022-03-05 368/week @ 2022-03-12 521/week @ 2022-03-19 118/week @ 2022-03-26 91/week @ 2022-04-02 81/week @ 2022-04-09 200/week @ 2022-04-16 245/week @ 2022-04-23 383/week @ 2022-04-30 673/week @ 2022-05-07 1626/week @ 2022-05-14

2,968 downloads per month


12K SLoC


crates.io CI commits-since rust 1.51.0+ badge

Check your spelling with hunspell and/or nlprule.

Use Cases

Run cargo spellcheck --fix or cargo spellcheck fix to fix all your documentation comments in order to avoid nasty typos all over your source tree. Meant as a helper simplifying review as well as improving CI checks after a learning phase for custom/topic specific lingo.

cargo-cpellcheck is also a valuable tool to run from git commit hooks or CI/CD systems.

Check For Spelling and/or Grammar Mistakes

cargo spellcheck check
error: spellcheck
   --> src/main.rs:44
 44 | Fun facets shalld cause some erroris.
    |            ^^^^^^
    | - shall or shall d

Apply Suggestions Interactively

cargo spellcheck fix
error: spellcheck(Hunspell)
    --> /media/supersonic1t/projects/cargo-spellcheck/src/literalset.rs:291
 291 |  Returns literl within the Err variant if not adjacent
     |          ^^^^^^

(13/14) Apply this suggestion [y,n,q,a,d,j,e,?]?

   liter l
 » a custom replacement literal


cargo install --locked cargo-spellcheck

The --locked flag is the preferred way of installing to get the tested set of dependencies.


cargo spellcheck completions for autodetection of your current shell via $SHELL,


cargo spellcheck completions --shell zsh

to explicitly specify your shell type.

Commonly it's use like this from your shell's .rc* file:

source <(cargo spellcheck completion)

Note: There is a relevant clap issue (#3508) that makes this fail in some cases.

🎈 Contribute!

Contributions are very welcome!

Generally the preferred way of doing so, is to comment in an issue that you would like to tackle the implementation/fix.

This is usually followed by an initial PR where the implementation is then discussed and iteratively refined. No need to get it all correct the first time!



~624K SLoC