---
name: anti-slop
description: Audit-then-fix pass for AI slop in any prose an agent writes or edits (docs, READMEs, PR descriptions, commit messages, emails, posts). Use before returning or committing any text, or when asked to "anti-slop", "unslop", "de-AI" or tighten writing.
---

# Anti-slop

Run two passes. Pass 1 audits and counts. Pass 2 fixes only what failed. Never invent facts, never change code, names, numbers, quotes or links.

## Pass 1: audit (count, don't fix yet)
Count each item in the draft and compare with the cap.

| # | Check | Cap |
|---|-------|-----|
| 1 | Throat-clearing openers ("It's worth noting", "In today's...", "Let's dive in") | 0 |
| 2 | Negative parallelisms ("it's not X, it's Y", "not just X but Y", "X isn't A. It's B.") | 0 |
| 3 | "Y rather than X" / "should be treated as" disclaimers | 1 per 500 words |
| 4 | AI vocabulary: crucial, delve, pivotal, robust, seamless, leverage, foster, showcase, underscore, multifaceted, vibrant, tapestry, testament, landscape (abstract) | 1 per 300 words |
| 5 | "serves as / stands as / boasts" where "is / has" works | 0 |
| 6 | Lists of exactly three used for rhythm | 1 per piece |
| 7 | Em dashes | 1 per 300 words |
| 8 | Bold run-in labels, emoji bullets, headings in short prose | 0 unless the format needs them |
| 9 | Chat residue: "I hope this helps", "Let me know if", "If you'd like, I can" | 0 |
| 10 | Summary closer that repeats the piece ("In short", "Overall", "Ultimately") | 0 |

Write the audit as a one-line tally, e.g. `audit: 2 negations, 3 vocab (cap 1), 1 em dash -> fix 1, 2, 4`.

## Pass 2: fix
- Delete before you rewrite. Most slop is removable without replacement.
- Negations: keep the true half, state it directly.
- Vocabulary: the plain word (crucial -> important or cut; leverage -> use; showcase -> show).
- Lists of three: keep the items that are true and needed, any number.
- Em dashes: comma, period, colon or parentheses.
- Keep the author's register. Don't add slang, typos or jokes to sound human.

## Pass 3: re-count
Re-run the table. If anything is still over its cap, fix once more, then stop. Report the final tally in one line.

## Code-adjacent text
- Commit messages: imperative subject under 72 chars, no "This commit...", no emoji.
- PR descriptions: what changed, why, how to test. No "This PR aims to enhance".
- Code comments: say why, not what. Delete comments that restate the code.

Free online checker with the same categories: https://gounslop.com/ai-slop-detector