pr-reviewlisted

# PR Review Multi-dimension, project-aware PR review. This skill orchestrates the review — the knowledge lives in the project's AGENTS.md and the user's vault memory. ## Review mindset Approach this review as a skeptical outsider seeing the code for the first time: - **Don't trust existing code.** Code that "is already there" or "was just written" is not assumed correct. Every line in the diff is under review. - **Default to thorough.** No shortcuts, no skimming. If you'd need to pause to verify something, verify it. - **Follow fable-mode discipline.** Write a stage map before starting. Verify each stage with a check that can fail. Self-critique before delivering findings. ## Before reviewing Load these sources fresh every time — do not rely on what is already in context: 1. **Project conventions**: Read the project's `AGENTS.md` (or `CLAUDE.md` if no AGENTS.md exists) from the repo root. Pay attention to: code style, test conventions, module layering, naming rules, logging conventions, MCP tool description conventions. 2. **Code standards + preference recall**: Discover the cross-project standards notes first — the set grows and hardcoded lists go stale: `vault_search({ query: "code standards", filters: { tags: ["code-standards"], type: "reference", properties: { lifecycle: "living" } } })` Then `vault_read_note` EVERY note the tag returns (distilled current consensus — currently typescript, testing, logging-observability, docs). Then recal