codebase-evidence-reviewlisted

# Codebase Evidence Review ## Purpose Produce answers that are grounded in the actual repository instead of product assumptions, docs-only reasoning, or visible UI labels. The user's repeated pattern is to ask for the real source path, real control fields, and real activation conditions before deciding whether to patch. ## When to use Use this skill for: - Codebase exploration, architecture tracing, source-backed explanations, PR/spec reviews, and bug triage. - Questions that compare a visible symptom with implementation reality, such as model labels, Slack threading, runtime ownership, or route behavior. - Review requests where findings must be actionable and tied to exact locations. Do not use it for pure brainstorming, copy editing, or tasks where the user explicitly says not to inspect files. ## Workflow 1. **Orient on the repo** - Run `pwd` and inspect the nearest `AGENTS.md`. - Use `rg --files` or `fd` to find likely entrypoints, tests, config, and docs. - Read the smallest set of files that can answer the question. 2. **Trace the primary path** - Identify the first real entrypoint: CLI command, route handler, monitor, hook, service, component, or worker. - Follow data and control flow to the final side effect. - Name the decisive symbols: functions, classes, fields, env vars, config keys, routes, and storage tables. 3. **Separate facts from hypotheses** - Mark as fact only what is proven by source, local files, tests, logs, or a direct com