SKILL35codebase-intelligence
Investigating a Codebase Semantically
Finds candidate implementations by behavioral intent, validates them in code, and rejects textual matches that do not establish ownership.
Primary benefit
Locates the code that owns a behavior without requiring the requester to know its symbol names, filenames, or repository vocabulary in advance.When to use
Use when you know what a behavior does but not where it is implemented, and candidate results must be validated against code, call sites, tests, or configuration.
When not to use
Do not use for a broad inventory of modules and boundaries; Mapping Existing Codebase Structure owns current-state structural mapping.
Use cases
Locate where a user-visible rule is enforced when the repository uses unfamiliar names
Distinguish the real owner of a behavior from comments, adapters, tests, generated files, and other semantic false positives
Example prompts
Use investigating-codebase-semantically to find and validate the implementation that owns this behavior. Report candidates and rejected false positives as observed, inferred, or unresolved, with source and location for each conclusion.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill investigating-codebase-semanticallyPowerShell
./install.ps1 --skill investigating-codebase-semanticallyChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.