Trace callstacks and diagnose root causes with filename:line logging.
npx skills add https://github.com/2lab-ai/oh-my-claude --skill debug-2lab-ai
Please help me install this Agent Skill. Skill: debug Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/debug Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill debug-2lab-ai
Provides a disciplined, repeatable methodology for diagnosing software that behaves differently than expected by tracing execution, recording findings, and isolating root causes to prevent regressions.
Start at the failing entry point, follow the callstack one step at a time into each file or service, and record each filename:line and conditional outcome into the trace log while iterating on single hypotheses and writing a reproduce-first test.
High-intent search queries and answers about installing and using this skill.
Trace the callstack step-by-step across files and services to find the root cause of a flaky test, recording exact filename:line observations and conditional outcomes into a persistent trace log to isolate the issue.
Blackbox callstack debugging is a methodology for diagnosing unexpected software behavior by following the callstack and recording each executed step. Use it when a production or test failure is non-obvious and requires reproducing failures and instrumenting traces.
Debug an unexpected conditional branch by starting with a top-3 heuristic check, then moving to exhaustive branch exploration to ensure no branch remains unexamined. Record each filename:line and conditional outcome into a trace log while iterating on single hypotheses.
The best way to reproduce a software failure and verify the fix is to use a red-green verification cycle: reproduce the issue with a failing test, implement a focused fix, and confirm the fix plus regression safety with layered guards.
Trace execution across services by following the callstack one step at a time into each file or service, writing exact filename:line observations to a persistent trace log, and applying exhaustive branch exploration when heuristic checks fail to locate the root cause.
Yes, this debugging approach works without external dependencies by using a blackbox tracing methodology. It follows the callstack step-by-step, recording each executed step and conditional outcome into a persistent trace log to locate root causes.
kynopticAnalyze stack traces and error logs to identify root causes and propose fixes.
MovchanetsDiagnose software errors by tracing stack traces to root causes.
TobiasBak...
WesleyMFrederickTrace root causes of errors through deep call stacks with instrumentation.
