civiltekk-ponytail-audit-skill

Consolidates ponytail-audit-skill + ponytail-review-skill + ponytail-debt-skill (#603).

What I do

Cut over-engineering, on three scopes:

1. Detect the route (§Routes) — explicit > inferred > ask-once.
   Explicit: the request names the scope ("audit for over-engineering",
   "find bloat", "what can I delete" → whole-repo-audit;
   "over-engineered diff", "simplify this change", "review for bloat" →
   diff-review; "ponytail shortcuts", "what did ponytail defer",
   "tech debt markers" → debt-ledger). Inferred: the artifact under
   review (a diff/PR → diff-review; the whole tree → whole-repo-audit;
   ponytail: comments or a deferral ledger → debt-ledger). Ambiguous
   ("is this over-engineered?") → ask once — one ask per run, then proceed
   on the answer.
2. Load the route's values file (references/audit.md /
   references/review.md / references/debt.md) and apply its contract.
3. The routes compose — a diff-review finding a ponytail: marker feeds
   debt-ledger; a whole-repo-audit pass may end with a ledger sweep.
   Load per request, not all three up front.

Side files (load rules)

Side files carry VALUES only; this file carries the METHOD. The shared tag
vocabulary lives in the values files (review.md defines it; audit.md and
debt.md reuse it). The runtime /ponytail ladder itself is the scoped
plugin (plugins/opencode-ponytail-scoped.ts), not this skill — this skill
is the on-demand reviewer/auditor.

Routes

Boundaries

• The three routes were formerly peer skills — those boundaries are internal
  now; the route table above is the boundary logic.
• Scope: over-engineering and complexity only. Correctness bugs, security
  holes, and performance are explicitly out of scope — route them to a
  normal review pass. Smell cataloging and KISS tradeoffs belong to
  code-smells-skill / complexity-management-skill; this skill cuts,
  those classify.
• All routes list findings and apply nothing; debt-ledger writes a file
  only on explicit ask. One-shot each.
• Mode switching ("/ponytail lite", "stop ponytail-audit", "normal mode")
  belongs to the scoped plugin and the values files' revert phrases.

Agent behavior rules

• One ask per run maximum (route detection); headless/CI: no asks — infer
  from the artifact (diff → diff-review; tree → whole-repo-audit;
  markers → debt-ledger).
• End every route with its closing metric (net: line or marker count) —
  "Lean already. Ship." / "Clean ledger." when nothing is found.
• Never flag a single smoke test or assert-based self-check for deletion
  (ponytail minimum, not bloat).