dag-execution-tracer
About
This skill traces complete execution paths in DAG workflows, recording node timing, inputs, outputs, and state transitions for debugging. Use it for execution tracing, path analysis, and logging when you need to understand workflow flow. It is specifically for execution path tracing, not for performance profiling or failure investigation.
Quick Install
Claude Code
Recommendednpx skills add majiayu000/claude-skill-registry -a claude-code/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/dag-execution-tracerCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
smart-bug-fix
TestingThis skill provides an automated bug-fixing workflow that performs root cause analysis, generates fixes with Codex, and validates changes with testing. It's designed for developers to systematically debug issues by combining multi-model reasoning with iterative validation. Use it when you need a structured, AI-assisted approach to diagnose and resolve complex bugs.
when-debugging-ml-training-use-ml-training-debugger
OtherThis skill helps developers diagnose and fix common machine learning training issues like loss divergence, overfitting, and slow convergence. It provides systematic debugging to identify root causes and generate fixes for training problems. Use it when you encounter poor validation performance or training instability to restore model convergence.
systematic-debugging
OtherThis skill provides a structured four-phase debugging framework to replace random code changes with systematic problem diagnosis. It helps developers methodically investigate bugs, errors, and unexpected behavior by forming specific hypotheses and testing single changes. Use it when under time pressure or when quick fixes seem obvious to ensure reliable problem resolution.
Root Cause Tracing
OtherThis skill systematically traces bugs backward through the call stack to identify their original triggers rather than just fixing symptoms. It's designed for use when errors occur deep in execution with unclear data origins or long call chains. The approach involves observing symptoms, finding immediate causes, and repeatedly asking "what called this" until reaching the source.
