What kind of diagrams does this skill generate?

It creates concise 5-10 line text diagrams that visualize the sequence of function calls, data types, and error propagation paths (Result types) within your code.

Does this work with specific architecture patterns?

Yes, it is optimized for functional patterns like fn(args, deps), Result-based error handling, and structured workflow composition.

How does this skill prevent guessing during development?

It requires specific file and line references for every step in the execution chain, forcing the AI to verify exactly where logic resides before suggesting any modifications.

When should I use the Code Flow Analysis protocol?

It is best used for non-trivial tasks like bug fixing, feature implementation, and refactoring. It can be skipped for minor changes like typos or documentation updates.

Code Flow Analysis

Name: Code Flow Analysis
Author: jagreehal

byjagreehal

Developer Tools

Maps execution paths using file:line references to ensure deep understanding before implementing code changes.

About

The Code Flow Analysis skill implements a rigorous protocol that forces Claude to trace the exact execution path of a system before modifying it. By requiring specific file and line references, visual flow diagrams, and validation of function dependencies, it eliminates guesswork and prevents unintended side effects. This skill is particularly effective for debugging complex bugs, implementing features within established architectures, and refactoring workflows that rely on Result types or functional composition patterns.

Key Features

Mandatory file:line execution tracing
Concise visual flow diagram generation
Functional dependency (args, deps) mapping
0 GitHub stars
Result type and error propagation tracking
Confirmation-based verification loop

Use Cases

Root cause analysis for complex bugs where the source of failure is not immediately obvious.
Refactoring legacy code by mapping current dependencies and execution flows before changing them.
Planning feature implementations to ensure alignment with existing architectural patterns.

About

Key Features

Mandatory file:line execution tracing
Concise visual flow diagram generation
Functional dependency (args, deps) mapping
0 GitHub stars
Result type and error propagation tracking
Confirmation-based verification loop

Use Cases

Root cause analysis for complex bugs where the source of failure is not immediately obvious.
Refactoring legacy code by mapping current dependencies and execution flows before changing them.
Planning feature implementations to ensure alignment with existing architectural patterns.