Investigate

Investigate

Read-only codebase Q&A. Trace code, not guesses. No file changes.

Do NOT use when

• Code changes are needed (use appropriate dev skill)
• The question is about planning (use align)
• The question is about security (use security-review)

Workflow

1. Search ck_memory_search for prior analysis on this area.
2. Trace actual code paths for the question type:
   • How: entry point → call chain → data flow → side effects
   • Why: git log --oneline -20 -- <file>, linked issues, commit messages
   • Where: search for function/module references, trace callers
   • What-if: trace the code path for that scenario, identify edge cases
3. Check multiple sources: source control, tests, comments. Code shows what, not why.
4. Answer concisely: direct answer + evidence (file:line, commit SHA) + caveats.

Rules

• Read-only — no file changes. If fix needed, record and recommend appropriate skill.
• Every claim backed by code evidence or git history.
• Answer what was asked — do not explore tangentially.
• Stop at external boundaries — say so instead of speculating.

Output

• Concise answer with file:line evidence
• Optional ck_memory_record for durable findings
• No file changes