audit

Pre-computed context

Current branch: !git branch --show-current 2>/dev/null || echo "unknown" Effective config: !"${CLAUDE_SKILL_DIR}/scripts/detect.sh" --show-config >/dev/null 2>&1 && { "${CLAUDE_SKILL_DIR}/scripts/detect.sh" --show-config 2>/dev/null | head -8; :; } || echo "detector unavailable"

Purpose

Detect and remove AI-writing tells in checked-in markdown prose. Two detection layers over one rule inventory (reference/catalog.md, distilled from Wikipedia's "Signs of AI writing", revision-pinned, plus the catalog's "Cursor unslop additions" section and its repo-owned, evidence-graded "Model-era additions" section of current-generation model vocabulary):

1. Deterministic: ${CLAUDE_SKILL_DIR}/scripts/detect.sh runs the catalog's v1: script rules. Its findings carry argued severity tiers (the detector-findings convention's crosswalk) and persist as a conforming findings file. What the relay APPLIES is narrow; what it ROUTES is not. rule-utm-params alone is auto-applicable, and every other rule is /ai-slop:audit fix work — but the crosswalk now declares that ownership, so the relay hands those rows to this skill's fix action rather than to its cleanup route, which prefers /simplify, a code-simplification skill, and applies the rows itself when /simplify is absent. Neither branch loads this skill's rewrite guide. The findings file is how a consumer sees them and how they reach the one surface that can rewrite them.
2. Judgment rubric: the catalog's v1: rubric tells, applied by reading the prose. Rubric findings reach the human report only, never the findings file.

Both layers sit behind the catalog's policy-level quotation exemption: wording rules never scan blockquotes, double-quoted spans, or inline code spans (typography rules still do), so a document that quotes a tell to document it, and a changelog that backticks the phrase a fix removed, stay marker-free by construction.