code-flow-analysis

Trace code execution paths through fn(args, deps) flows and Result propagation.

3|1|Updated Jan 4, 2026

Search Tags:#typescript #workflow #debugging #diagrams #code-flow #Result-types

Ready to run

npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill code-flow-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-flow-analysis
Source: https://github.com/jagreehal/jagreehal-claude-skills/tree/main/skills/code-flow-analysis
Command: npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill code-flow-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace code execution paths to understand and fix bugs before making changes.

Core Features & Use Cases

Map entry points and function chains that use fn(args, deps) patterns.
Visualize Result propagation and workflow composition to prevent guessing.
Apply the protocol during debugging, feature work, or refactoring to ensure safe updates.

Quick Start

Trace an example: identify the entry point, the fn(args, deps) sequence, and the Result flow; create a short, readable diagram; then proceed with targeted fixes and tests.

Frequently Asked Questions about code-flow-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace code execution paths before fixing bugs in TypeScript?▼

Trace code execution paths by mapping entry points, fn(args, deps) sequences, and Result type propagation. This visualization prevents guessing during debugging, feature work, or refactoring, ensuring safe and predictable code updates before you make changes.

What is the best way to visualize Result type propagation in a TypeScript workflow?▼

Visualize Result type propagation by creating lightweight execution diagrams that map workflow compositions and fn(args, deps) function chains. This clarifies how Result types flow through your code, preventing unexpected side effects during refactoring or bug fixes.

How do I debug a TypeScript workflow composition without guessing?▼

Debug TypeScript workflow compositions by tracing the fn(args, deps) execution flow and Result type propagation with file:line references. Generating a readable diagram guides targeted fixes and tests, removing guesswork from the process.

Do I need file:line references to map code flow during refactoring?▼

Yes, file:line references are required to accurately trace code flow during refactoring. They pinpoint exact execution paths within fn(args, deps) sequences and Result type flows, providing the clarity needed for safe and targeted code updates.

When should I trace code flow instead of directly applying fixes?▼

Trace code flow before applying fixes during debugging, feature work, or refactoring. Mapping the execution path and Result type propagation beforehand ensures you understand the root cause, preventing unpredictable updates and guiding safe modifications.

Can I use code-flow-analysis for debugging TypeScript Result types?▼

Yes, you can use it to debug TypeScript Result types by tracing their propagation across workflow compositions and fn(args, deps) function chains. It generates lightweight diagrams to visualize the flow, ensuring safe and predictable updates.