القائمة
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'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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"]} |
Read-only codebase Q&A. Trace code, not guesses. No file changes.
align)security-review)ck_memory_search for prior analysis on this area.git log --oneline -20 -- <file>, linked issues, commit messagesck_memory_record for durable findingsRun 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.
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.
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.
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.
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.
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.