SKILL60codebase-intelligence
Tracing Code Execution Paths
Reconstructs an ordered execution path from trigger to terminal behavior across code and service boundaries while separating observed transitions from inference.
Primary benefit
Makes runtime-relevant flow reviewable without overstating reachability, correlation, or textual matches as proven behavior.When to use
Use when you need to follow how a request, event, command, job, or user action moves through handlers, modules, integrations, and terminal behavior in an existing codebase.
When not to use
Do not use to diagnose why a failure occurs or claim root cause; Systematic Debugging owns hypothesis testing and root-cause investigation.
Use cases
Trace an API request from its route through authorization, business logic, persistence, and response construction
Reconstruct how an asynchronous event crosses producers, queues, consumers, and downstream side effects
Example prompts
Use tracing-code-execution-paths to reconstruct the ordered path from this trigger to terminal behavior, including boundary crossings and unresolved jumps. Label transitions as observed, inferred, or unresolved and cite each source and location.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill tracing-code-execution-pathsPowerShell
./install.ps1 --skill tracing-code-execution-pathsChatGPT
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.