Testing & Debugging Skills

Run a rigorous, repeatable, convergent audit of a codebase covering schema integrity, data flow, security, concurrency, resource bounds, spec compliance, operational readiness, test coverage with spec→acceptance-test mapping, and diagnosability. Use whenever the user asks to audit, review, QA, verify, or validate a codebase — especially before a release or after a major refactor. Consumes cartographer's codemap for targeted retrieval; produces a persistent AUDITLOG.md so audits converge across rounds. Pre-commit-verification first for a clean baseline; invokes spec-bootstrap when no design spec exists; hands off to audit-fix at the end.

Maps and documents codebases of any size by orchestrating parallel subagents.

Use when the user asks to verify, test, check, validate, or confirm their repo before committing or pushing — including requests like "do a pre commit verification", "run local tests before push", "deep local verification", "fix everything and test it", "make sure this is ready", or "run the full verification pass". Covers stack-aware test discovery, unit/integration/e2e tests, smoke tests, lint checks, type checks, builds, and a runtime smoke/integration harness (binary-launch, migration idempotency, provider mocks, headless webview, env probe) for desktop apps. Do NOT use for a single narrow test unless explicitly requested.

Reconstruct a design spec (SPEC.md) for a codebase that doesn't have one — derive observed behavior from the code, interview the user to separate intent from accident, and produce a section-numbered, provenance-marked spec that app-audit can generate its checklist from. Use when the user asks to write or create a design spec, document what the app should do, or formalize requirements for an existing app — and automatically when app-audit Phase 1 finds no spec. Every statement is marked [confirmed] / [observed] / [assumed] so audits know how much to trust each claim.