Menu
Use when entering an unfamiliar repository or subsystem and you need a disciplined search-and-read strategy before changing code.
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.
Based on SOC occupation classification
Use when debugging a failing test, broken build, runtime error, or unexpected system behavior. Drives hypothesis-based investigation, root-cause fixes, verification, and reusable learning capture.
Use when a claim, plan, spec, doc, or design must be attacked against source evidence before implementation or approval. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when fixing broken behavior and the priority is reproduce, root cause, regression proof, and the smallest safe repair. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when reviewing code changes with explicit stage, target, and focus so own-code checks and others’ PR reviews stay distinct but share one contract. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when the deliverable is docs or reference material and every claim must stay tied to observed behavior or cited source evidence. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
Use when adding or changing product behavior that must ship with explicit purpose, scenarios, and verification. Uses write tools, shell execution, and may spawn subagents. Invoke with enable_write_tools=true and enable_subagent_tools=true.
| name | codebase-exploration |
| description | Use when entering an unfamiliar repository or subsystem and you need a disciplined search-and-read strategy before changing code. |
Use this skill before editing an unfamiliar codebase, package, or subsystem.
README.md or the nearest project overview.package.json, Cargo.toml, go.mod, or equivalent.packages/cli/library/ source files first, then the affected generated tool-native outputs.Stop and ask for direction when: