Detecting AI Smell

Scan the text for these seven patterns, flag each instance, then rewrite to remove it while preserving meaning:

1. Contrastive antithesis: "This isn't just a bug, it's a symptom of a deeper problem."
2. Self-labeled honesty: "To be honest, this approach has issues." / "I'll be transparent with you."
3. Hollow emphasis: "It's important to note that..." / "This is crucial." (with no payoff)
4. Casual gloss over precise term: "the thing that checks if it's valid" instead of "the validator"
5. Robotic caveat-lists: "However, there are a few considerations: 1) ... 2) ... 3) ..."
6. Adjective doublets: "clear and concise", "robust and scalable", "simple yet powerful"
7. Superlative marketing: "game-changing", "revolutionary", "seamlessly", "unlock the full potential"

Example rewrite:

• Before: "This isn't just a refactor, it's a complete reimagining of the architecture. To be honest, it's robust and scalable, and it will seamlessly unlock the full potential of the system."
• After: "This rewrites the architecture. It handles 10x current load without new failure modes."

Progress:

• Read the full text once without editing
• Mark every instance of the 7 patterns (quote the exact phrase)
• For each flagged phrase, determine what concrete claim it's gesturing at
• Rewrite each flagged phrase with that concrete claim, or delete it if there is none
• Re-read for rhythm — not every sentence needs to be short, but variance should look human
• Do a final pass for newly introduced instances (rewrites often reintroduce doublets/emphasis)

Pattern-by-pattern fixes

Contrastive antithesis ("X, not Y") Flag: "This is X, not Y" / "not just X, it's Y" / "isn't about X, it's about Y" Fix: State the actual claim directly. Only keep a contrast if both sides are genuinely informative and the writer would naturally think in those terms.

• Bad: "This isn't a limitation, it's a feature."
• Good: "This forces callers to handle the empty case explicitly."

Self-labeled honesty/transparency Flag: "honestly", "to be honest", "I'll be transparent", "in all transparency", "let me be direct", "frankly" Fix: Delete the label. Just say the thing. Labeling honesty implies the rest of the text isn't, which is itself suspicious.

• Bad: "Honestly, the tests are flaky."
• Good: "The tests are flaky."

Hollow emphasis Flag: "it's important to note", "it's worth mentioning", "crucially", "this is key", "notably" — when removing the phrase loses nothing. Fix: Delete the phrase; if the content after it is actually important, let it stand on its own or show why via a concrete detail (number, consequence, example).

• Bad: "It's important to note that this runs on every request."
• Good: "This runs on every request, adding ~40ms per call."

Casual gloss over precise term Flag: a vague paraphrase used where the field has a standard term ("the thing that watches for changes" → "the observer"; "numbers that don't change" → "constants"). Fix: Use the precise term. Only gloss if the audience is confirmed non-expert.

Robotic caveat-lists Flag: formulaic enumerated hedges, especially triads: "There are a few things to consider: 1)... 2)... 3)..." or "However, keep in mind:" Fix: Fold the single most relevant caveat into the sentence naturally. Drop the rest unless each is load-bearing.

• Bad: "However, there are a few considerations: 1) performance, 2) readability, 3) maintainability."
• Good: "The tradeoff is readability — it's about 15% slower."

Adjective doublets Flag: paired adjectives/adverbs joined by "and"/"yet" that add no distinct information: "clear and concise," "robust and reliable," "simple yet powerful," "fast and efficient." Fix: Pick the one word that's actually true, or replace both with a concrete fact.

• Bad: "a clean and elegant solution"
• Good: "a 12-line solution" or just "a clean solution"

Superlative marketing Flag: "game-changing", "revolutionary", "cutting-edge", "unlock", "seamless(ly)", "supercharge", "elevate", "robust" (as filler), "unleash", "state-of-the-art" (unless literally true and cited). Fix: Delete or replace with a measurable claim. If no measurable claim exists, the sentence probably shouldn't exist.

Example 1: Input: "This refactor isn't just about cleaner code, it's about building a more scalable and maintainable foundation for the future. To be transparent, there are a few things to keep in mind: 1) it touches the auth module, 2) it's a breaking change, 3) tests need updating." Output: "This refactor touches the auth module and breaks the public API, so tests need updating. In exchange, adding a new auth provider is now a 20-line change instead of 200."

Example 2: Input: "Honestly, the new caching layer is a game-changer — it seamlessly unlocks blazing-fast performance across the board." Output: "The new caching layer cuts median response time from 300ms to 40ms."

Example 3: Input: "It's worth noting that the function that checks if the input is okay doesn't handle null, which, to be fair, isn't just an edge case — it's a fundamental gap." Output: "The validator doesn't handle null input, which will throw on about 5% of production requests."