Diagnose software bugs through a six-phase feedback-loop methodology.
npx skills add https://github.com/tonomb/personal-pnl --skill diagnosing-bugs-tonomb
Please help me install this Agent Skill. Skill: diagnosing-bugs Source: https://github.com/tonomb/personal-pnl/tree/main/.agents/skills/diagnosing-bugs Command: npx skills add https://github.com/tonomb/personal-pnl --skill diagnosing-bugs-tonomb
This skill solves the problem of aimless debugging by enforcing a structured, evidence-based feedback loop that prevents premature hypothesis generation and ensures bugs are reproduced and verified before a fix is applied.
Invoke the diagnosing-bugs skill to begin a structured debugging session for the reported issue by following the phase-based instructions provided in the documentation.
High-intent search queries and answers about installing and using this skill.
Fixing non-deterministic crashes requires a structured, evidence-based feedback loop that mandates a deterministic, minimal reproduction case before attempting any code changes to prevent speculative fixes.
You can build a deterministic reproduction loop for software debugging by following a structured six-phase protocol that prioritizes evidence-based instrumentation, ensuring the reproduction command is minimal, fast, and reliably red-capable before fixing.
Premature hypothesis generation fails during root cause analysis because it leads to aimless debugging and speculative code changes instead of relying on verified evidence gathered from a tight, deterministic reproduction loop.
Structured troubleshooting for complex bugs involves six distinct phases: building a reproduction loop, minimizing the repro, generating hypotheses, instrumenting for evidence, applying the fix, and conducting a post-mortem.
You can use this debugging methodology for performance regressions across any platform, as it operates across the entire development lifecycle and enforces a mandatory feedback-loop-first approach independent of specific dependencies.
You should avoid speculative code changes for troubleshooting when dealing with complex bugs or performance regressions, as this structured approach requires verified instrumentation and a minimal reproduction case before any fix is applied.
danielcopperApply a six-phase debugging framework to resolve software defects and performance regressions.
davekilleenGenerate structured incident post-mortems with root cause analysis and action items.
InditexTechDiagnose bugs and performance regressions through a structured reproduction-to-verification workflow.
yashs33244Reduce verbosity in code writing, review, debugging, and refactoring outputs.
