v3.7.0
New: AP-34 — Gotchas / troubleshooting bloat
A new anti-pattern for the case where a "Gotchas / 踩坑" section quietly grows into a per-incident log — each entry a full symptom → cause → fix narrative — until it dominates the main skill file. It is the structural sibling of AP-33 (version-history bloat): both push volatile, append-only detail into the file that should stay lean.
New: L1-8 automated check
The audit script now measures the Gotchas section: it counts ### entries and the section's share of total lines, and emits an info-level warning when there are more than 10 entries or the section exceeds 40% of the file. Like the L1-5 line-count check, this is advisory — never a hard fail.
Tiered remedy guidance
Each flagged Gotchas item is triaged three ways:
- Delete — already covered by the workflow or a rule; redundant.
- Uplift — an actionable conclusion that belongs as a step in the main workflow.
- Sink — an implementation-specific pitfall that moves to
references/troubleshooting.md, leaving only a short symptom → lookup index in the main file.
Rule of thumb: needed during normal execution → uplift; only needed when touching one specific thing → sink; stated elsewhere → delete.
Counts
- Audit model: 52 → 53 items (27 auto-scannable)
- Anti-pattern catalog: 33 → 34
Synced across SKILL.md, the audit script, quality-gates reference, both READMEs, and the landing page.