← ClaudeAtlas

dogfood-clilisted

Hunt for real bugs in the vigiles CLI/codebase with a parallel expert fan-out, then FIX them directly — source-trace each defect to file:line, add a regression test, commit per theme. Use when asked to dogfood vigiles, find/fix bugs across the CLI the source-traced way, or fan out agents to audit the tool on itself.
zernie/vigiles · ★ 15 · AI & Automation · score 73
Install: claude install-skill zernie/vigiles
# Dogfood the vigiles CLI (expert find + fix fan-out) The repeatable method for finding real bugs in vigiles by running the tool on itself and on real plugins, then FIXING them — not filing them. This is how the 2026-07 batch found and fixed 14 source-traced bugs. ## When to use - "Dogfood the CLI", "find more bugs the source-traced way", "fan out agents to audit vigiles on itself", "hunt for false positives in audit/lint". - NOT for a single known bug (just fix it) and NOT for shipped consumer features (this is a contributor-only dev process; `.claude/` is not published). ## The loop ``` fan out (parallel experts) → synthesize + VERIFY each finding → fix directly → regression test → build → targeted test → commit per theme → FULL SUITE → push ``` ### 1. Fan out over DISTINCT surfaces Spawn several agents (Sonnet — cheap parallel reads/traces; no synthesis needed per agent), each owning ONE surface so they don't overlap. The surface map that has paid off: - **compile / eject** — round-trip correctness, frontmatter/data loss, integrity. - **audit / lint false-positives** — a real plugin must stay CLEAN (don't cry wolf); phantom paths; glob/quote tokens misread; comment-only matches. - **init / scaffold edge cases** — no `package.json`, config-driven `harness`, malformed frontmatter, `--target`, the scaffolded CI workflow, `--test`/`--lint`. - **config parse-don't-validate** — `.vigilesrc.json` severities (`"off"`/0/1/2), string-or-array keys, unknown value