typos VS grammarly-api

There is typos though that takes a bit different of an approach to spell checking. When the default is to ask the user (like in a text editor), a regular spell checker is likely better. typos is more meant for being run in an automated fashion.

I recommend you run https://github.com/crate-ci/typos

Oh yeah, I can see you short hashes being a problem. The challenge has been finding the right heuristic for them

Is there good usage examples for this tool? typos simply traverses directories on invocation, wonder if there's a static analysis equivalent for ltrs.

highly recommend adding https://github.com/crate-ci/typos to your CI...very easy to add to a github action, catch fun spelling errors even in camelCased and snake_cased variable names...catch em before they become public facing APIs

I like to use https://github.com/crate-ci/typos as a command-line option. It's built to run as a service or in CI... I run it in our code review software and it has been a big hit.

there's a little comparison table here https://github.com/crate-ci/typos/blob/master/docs/comparison.md

typos

I'd love a GitHub Action that (unofficially) integrates Grammarly with GitHub checks. Just like the unofficial VS Code extension: https://github.com/znck/grammarly#grammarly

There is an unofficial SDK for TypeScript (maybe other languages too) so this shouldn't even be too hard: https://github.com/stewartmcgown/grammarly-api#unofficial-gr...