patpat-unslop

Cut AI tells, superficial patterns, and fluff from text or diffs.

SKILL.md

GitHub

Patpat Unslop

Before following this skill, apply the skill state and mutation gate.

Review engineering documentation, PR text, and code diffs for artificial writing artifacts and fluff. Preserve technical meaning, context, and the author's intended voice.

Process

  1. Scan text against the pattern catalog below.
  2. Report concrete rewrite recommendations that preserve exact technical meaning with natural, concise phrasing.
  3. Replace vague hand-waving with concrete references, code symbols, or numbers.

Pattern Catalog

Content and Substance

  1. Superficial participial clauses. Eliminate ungrounded -ing trailing clauses such as "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Replace with active statements or concrete causal evidence.
  2. Vague attributions. Eliminate "Industry standards suggest", "Experts believe", "Many developers prefer". Name the concrete specification, RFC, or team constraint, or delete the phrase.
  3. Empty summary filler. Remove introductory or concluding cheerleading phrases like "In summary, this change enhances stability" or "It is worth noting that...". State the technical fact directly.

Language and Vocabulary

  1. Inflated vocabulary. These words are often vague or inflated. Replace them only when the alternative preserves the exact claim and tone:
    • additionally -> also or merge sentences
    • crucial / pivotal -> required or necessary
    • delve -> inspect or investigate
    • enhance -> improve or name the concrete modification
    • foster -> allow or enable
    • intricate -> complex or specify the architecture
    • landscape -> context or specify the system
    • tapestry -> remove or replace only when decorative; preserve literal or domain-specific uses
    • testament -> name the specific evidence when used as vague praise; preserve literal uses
    • underscore -> show or confirm
    • vibrant -> remove or replace only when decorative; preserve literal or domain-specific uses
  2. Fancy copulas. Replace "serves as", "stands as", "boasts", "features" with simple "is" or "has".
  3. False contrasts. Eliminate "Not only X, but also Y" structures. State both facts plainly.
  4. Rule-of-three bias. Do not force lists or arguments into groups of three. Use the natural, accurate count.
  5. Synonym cycling. Avoid rotating synonyms for the same entity ("the caller, the invoker, the consumer"). Pick the canonical domain term and stick with it.
  6. Fake ranges. Eliminate "from X to Y" when X and Y are not points on a continuous scalar spectrum. Use an exact list.

Style and Punctuation

  1. Em dash overuse. Remove an em dash used only to join clauses. Keep it when it marks a parenthetical aside, interruption, attribution, or quoted source; prefer simpler punctuation only when it preserves the same meaning and voice.
  2. Excessive bullet nesting. Prefer flat, compact bullet points or code blocks over multi-nested outlines.
  3. Apologetic or sycophantic tone. Never use "Certainly!", "I would be happy to...", or "You are absolutely right!". State technical findings and decisions neutrally.
  4. Narrative code commentary. Strip conversational commentary from code changes. Code should communicate via types, names, and explicit structure.
  5. Unproven claims. Never state that a fix works or tests pass without attaching fresh, observable command receipts.

Mutation boundary

Remain read-only with respect to repository implementation and external delivery. Limit incidental verifier artifacts to the declared proof contract, clean them up, and hand any authorized mutation back to patpat-loop.