code-tracelisted

# Code Trace Use the smallest mode that answers the question. The default stance is evidence-first and read-only: inspect the repository, trace the relevant boundary, and report what remains unknown. A diagnosis may recommend a repair or a regression test, but it does not implement the repair. ## Modes | Mode | Use when | Completion criterion | |---|---|---| | `explore` | You need to understand an unfamiliar symbol, file, module, or flow. | Entry point, caller/callee path, evidence, assumptions, and gaps are recorded. | | `diagnose` | A failure, regression, performance problem, data inconsistency, or timing issue needs a confirmed cause. | One falsifiable root cause is supported by evidence, or the current blocker and next check are explicit. | | `history` | You need to know when, why, or by whom behavior changed. | Blame, timeline, original/problematic comparison, and actionable conclusion are reported. | | `select-tool` | You need one code-navigation tool and a fallback chosen. | One intent row, executable primary call, and concrete fallback or `none` are returned. | If `--mode` is omitted, infer one mode only when intent is unambiguous. A request to edit a symbol first requires the repository's impact-analysis rule before any implementation lane touches it; this skill only reports the impact. ## When NOT to Use - Implement a confirmed change → use `flow-drive`. - Review a proposed change → use `change-verdict`. - Author or audit a skill → use `skill-forge` or `skill-