Can it trace execution across multiple files?

Yes, the skill is designed to navigate the entire codebase, following function calls and imports across file boundaries to build a complete sequence from entry point to leaf function.

When should I use the /trace-execution command?

Use it when you need to understand exactly how a piece of data is handled, why a specific branch is taken, or when you need a formal map of a complex logical flow for documentation.

What do the [STATIC] and [BEHAVIORAL] tags mean?

These classification tags indicate the level of verification: [STATIC] means verified by reading code, while [BEHAVIORAL] indicates logic that might require runtime execution to confirm 100%.

How does this differ from standard code reading?

Standard reading often relies on naming conventions; this skill uses a structured format that forces Claude to provide line-number evidence and resolve dynamic dispatch, preventing logical hallucinations.

Trace Execution

Name: Trace Execution
Author: nicholls-inc

bynicholls-inc

•

Security & Testing

Performs hypothesis-driven execution path tracing to build complete, evidence-based call graphs from entry points to leaf functions.

This skill empowers Claude to perform rigorous, structured exploration of codebases by following execution paths from specific entry points. Instead of guessing behavior based on naming conventions, it utilizes a formal hypothesis-driven methodology that requires documenting line-by-line observations, resolving dynamic dispatch, and identifying key decision points. It is particularly useful for debugging complex logic, performing security audits, or onboarding onto large repositories where understanding the exact flow of data and control is critical for system stability.

Key Features

01Standardized claim classification including Static, Semantic, Behavioral, and Formal tags

02Automatic generation of complete call sequences with line-level evidence

033 GitHub stars

04Resolution of dynamic dispatch and polymorphism to identify actual runtime implementations

05Identification of side effects, branching conditions, and external system boundaries

06Hypothesis-driven structured exploration to prevent AI guesswork

Use Cases

01Tracing a complex authentication flow to identify exactly where a specific error originates

02Mapping data transformation steps of an API request from the controller through to leaf functions

03Performing security impact analysis by following untrusted input through the entire call stack

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nicholls-inc/claude-code-marketplace trace-execution

For use in Claude.ai and ChatGPT

Key Features

01Standardized claim classification including Static, Semantic, Behavioral, and Formal tags

02Automatic generation of complete call sequences with line-level evidence

033 GitHub stars

04Resolution of dynamic dispatch and polymorphism to identify actual runtime implementations

05Identification of side effects, branching conditions, and external system boundaries

06Hypothesis-driven structured exploration to prevent AI guesswork

Use Cases

01Tracing a complex authentication flow to identify exactly where a specific error originates

02Mapping data transformation steps of an API request from the controller through to leaf functions

03Performing security impact analysis by following untrusted input through the entire call stack

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nicholls-inc/claude-code-marketplace trace-execution

For use in Claude.ai and ChatGPT