investigate

Stars11

Forks0

UpdatedMay 29, 2026 at 18:59

Read-only codebase Q&A: trace code paths, answer how/why/where questions without changes. Trigger: 'how does X work', 'why was Y built this way', 'trace the data flow'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

aryaminus

aryaminus/controlkeel

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	investigate
description	Read-only codebase Q&A: trace code paths, answer how/why/where questions without changes. Trigger: 'how does X work', 'why was Y built this way', 'trace the data flow'.
when_to_use	Activate for read-only exploration questions. Do NOT use when code changes are needed.
argument-hint	[question about the codebase]
disable-model-invocation	true
license	Apache-2.0
compatibility	["opencode-native","claude-standalone","cursor-native","codex"]
metadata	{"author":"controlkeel","version":"1.1","category":"exploration","ck_mcp_tools":["ck_memory_search"],"related_skills":["architect-first"]}

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

Search ck_memory_search for prior analysis on this area.
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
Check multiple sources: source control, tests, comments. Code shows what, not why.
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

More from this repository

same repository

bounded-loop

aryaminus/controlkeel

Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.

2026-07-1711

communication-style

aryaminus/controlkeel

Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.

2026-07-1711

controlkeel-governance

aryaminus/controlkeel

Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.

2026-07-1711

cost-optimization

aryaminus/controlkeel

Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.

2026-07-1711

end-of-shift

aryaminus/controlkeel

Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.

2026-07-1711

false-confidence-test-audit

aryaminus/controlkeel

Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.

2026-07-1711

name	investigate
description	Read-only codebase Q&A: trace code paths, answer how/why/where questions without changes. Trigger: 'how does X work', 'why was Y built this way', 'trace the data flow'.
when_to_use	Activate for read-only exploration questions. Do NOT use when code changes are needed.
argument-hint	[question about the codebase]
disable-model-invocation	true
license	Apache-2.0
compatibility	["opencode-native","claude-standalone","cursor-native","codex"]
metadata	{"author":"controlkeel","version":"1.1","category":"exploration","ck_mcp_tools":["ck_memory_search"],"related_skills":["architect-first"]}

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

Search ck_memory_search for prior analysis on this area.
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
Check multiple sources: source control, tests, comments. Code shows what, not why.
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