investigatelisted

Investigate a codebase question or concern. **This is a read-only skill — do not modify any files.** Question or concern: $ARGUMENTS ## Instructions Follow these phases in order. Apply all project rules and conventions that are in your context. This skill is **read-only**. Do not checkout another branch, pull from remotes, fetch, stash, or otherwise mutate repo state — even "preparatory" steps. Investigate the current branch. If you need a fresher base ref than the local `origin/main`, ask before refreshing it. --- ### Phase 1: Scope 1. Parse the question or concern — is it about behavior, architecture, performance, a failure, a dependency, or something else? 2. If the scope is ambiguous, ask the user to clarify before proceeding. 3. Identify the likely entry points in the codebase (files, modules, services). **Gate:** The investigation scope is clear and bounded. --- ### Phase 2: Research Use read-only tools only. Do not edit, write, or create any files. 1. **Trace code paths** — read the relevant source files, following the call chain from entry point to the area of interest. 2. **Read tests** — understand what is tested and what is not. Look for edge cases and assumptions. 3. **Check git history** — use `git log --all -S "<term>"` to find when relevant code was introduced or changed. Use `git blame` for context on specific lines. 4. **Check dependencies** — if the question involves a library or framework, look up its documentation (use context7 if available). 5