ai-slop-linterlisted

# ai-slop-linter You write a lot of prose: commit messages, pull request descriptions, docs, release notes. Most of it carries the same tells, and readers have learned to skip text that carries them. This skill makes you check before you hand text over. ## When to run it Run the linter on anything longer than one line that a person will read, before you call the work done: - a commit message you are about to commit - a pull request title and body - a README, CHANGELOG entry, doc page or article you wrote or edited - an answer the user asked you to draft for someone else ## How to run it ``` npx ai-slop-linter path/to/file.md # a file, exits 1 on errors printf '%s' "$TEXT" | npx ai-slop-linter - # text you have in hand npx ai-slop-linter --commit # the last commit message npx ai-slop-linter path/to/file.md --fix # apply the safe fixes in place ``` Read the output top to bottom. Each line is `line:col severity rule message`. The message says what to do. Apply every fix yourself rather than only running `--fix`: `--fix` handles dashes, curly quotes and filler phrases, and leaves the rest to you because those need a sentence rewritten, not a character swapped. The file grades A to F. Aim for A on anything you ship. Do not add `slop-ignore` comments to make a file pass; rewrite the sentence. ## If the CLI is not available Check the text by hand against the rules. Fix each one you find. **Errors** (never ship these) - Em dashes and en dash