bug-checklisted

# Bug Check Systematic hunt for bugs that survive intuitive code review. This skill applies **pattern-based checks** derived from what Qodo and CodeRabbit consistently find that human and AI reviewers miss. How this differs from pr-review: pr-review reads the diff holistically and reasons about what could go wrong. Bug-check applies a **checklist of known miss patterns** to every changed file. It is systematic where pr-review is intuitive. ## Before starting 1. Load AGENTS.md for project conventions. 2. Load code standards + preference recall — discover the standards notes first (the set grows; hardcoded lists go stale), read the pass-relevant results, then recall the dated evidence trail for the change's domain (surfaces preferences newer than the notes): - `vault_search({ query: "code standards", filters: { tags: ["code-standards"], type: "reference", properties: { lifecycle: "living" } } })` - `vault_read_note` the results (currently typescript and docs), plus any newer note matching the repo's language/stack - `vault_memory_recall({ query: "<change domain>" })` 3. Identify all files changed in the branch vs main: ``` git diff main --name-only ``` 4. **Scope check**: Production code (`.ts`, `.js`), infrastructure (`.yml`, `.yaml`, `Dockerfile`, `docker-compose*`), environment config (`.env`, `.env.*`, `.env.example`), and config files (`sst.config.*`, `*.json`) are in scope. CI/workflow files ARE in scope — dimension 1 (descript