Systematic Debugging
ListedSystematically identifies and resolves software bugs using a structured debugging process guided by Johnsonmao's methodology.
Install on your platform
systematic-debugging. johnsonmao/skills is deleted or private, so it cannot be installed from.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.
What we know about this skill
Publisher
johnsonmao
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
This skill, johnsonmao-systematic-debugging, provides a structured approach to debugging code. It helps identify root causes of errors through methodical investigation and hypothesis testing. The agent can systematically analyze error messages, trace execution paths, and propose potential fixes based on observed behavior.
When to use it
- Complex Bugs: When facing difficult bugs that are not immediately obvious.
- Reproducibility Issues: To diagnose issues where a bug only appears intermittently.
- Production Errors: To analyze errors occurring in live environments and pinpoint the underlying cause.
- Debugging unfamiliar codebases: Provides a framework for understanding and troubleshooting new projects.
Key capabilities
- Systematic error analysis
- Hypothesis generation and testing
- Execution path tracing
- Root cause identification
- Potential fix suggestions
Example prompts
- "Debug this Python script: [script content]. The error message is: [error message]."
- "I'm seeing intermittent failures in my application. Use systematic debugging to find the root cause."
- “Trace the execution path of this function and identify why it’s returning an unexpected value.”
Tips & gotchas
The skill is most effective when provided with detailed error messages and context about the code being debugged. It may require iterative prompting and refinement of hypotheses to reach a conclusive diagnosis.