Diagnose and fix software errors through systematic root cause analysis.
npx skills add https://github.com/drafael/dotfiles --skill debug-error-drafael
Please help me install this Agent Skill. Skill: debug-error Source: https://github.com/drafael/dotfiles/tree/main/.agents/skills/debug-error Command: npx skills add https://github.com/drafael/dotfiles --skill debug-error-drafael
This Skill provides a structured, step-by-step methodology to systematically diagnose and resolve errors, bugs, and unexpected issues in software or systems.
NullPointerException in their application logs, they can use this Skill to follow a methodical approach to pinpoint the exact cause and implement a robust solution.Use the debug-error skill to troubleshoot the recent database connection failure.
High-intent search queries and answers about installing and using this skill.
Systematic debugging requires a structured methodology covering error reproduction, stack trace analysis, and root cause identification. This ensures you resolve the fundamental issue rather than applying a superficial fix to your software.
To find the root cause via stack trace analysis, gather error information, reproduce the issue, and investigate the code paths in the trace. Formulate hypotheses and validate data to pinpoint the exact failure point before implementing a fix.
Troubleshoot concurrency issues by monitoring resources and investigating thread interactions within your system. A systematic debugging methodology helps identify race conditions and validate dependencies to isolate the root cause of the bug.
Implement prevention measures after resolving a bug by conducting a post-resolution review, adding monitoring, and documenting the fix. This systematic approach ensures the error does not reoccur and improves overall system stability.
Yes, you can apply this systematic debugging methodology to any software system error. It provides a comprehensive framework independent of specific platforms, guiding you from initial error information gathering to final post-resolution review.
If your bug fix is not working during testing, revisit your root cause analysis and validate your initial hypothesis. Re-examine dependencies and resource monitoring data to ensure the underlying system error was correctly identified.
chicanoandres702Correlate logs, stack traces, and anomalies to diagnose distributed system errors.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
mwayIdentify root causes of bugs and test failures through a four-phase debugging workflow.
slantviewCorrelate error patterns and stack traces across logs and codebases.