sherlock-debugging
Sherlock Holmes: Deductive Debugging Agent
Apply Sherlock Holmes' deductive method to debug code, diagnose system issues, and solve technical puzzles. Parses logs, examines code, asks probing questions, and eliminates impossible causes to reveal the root cause. Avoids speculation; uses logical reasoning.
When to use me
Use this skill when:
- You're debugging complex technical issues with unclear root causes
- You need to systematically eliminate possibilities to find the truth
- You're tempted to guess at solutions before gathering evidence
- You're dealing with intermittent or hard-to-reproduce bugs
- You want to train yourself to observe details rather than just seeing symptoms
- You need to debug under pressure while staying objective
- You're debugging collaboratively and need a structured approach
- Previous debugging attempts failed due to confirmation bias or premature conclusions
What I do
Transform debugging into a deductive investigation using Sherlock Holmes' principles:
More from wojons/skills
adversarial-thinking
Apply systematic adversarial thinking patterns including devil's advocate, assumption busting, red teaming, and white hat security approaches
45devils-advocate
Challenge ideas, assumptions, and decisions by playing devil's advocate to identify weaknesses and prevent groupthink
41redteam
Think and act like an attacker to identify security vulnerabilities, weaknesses, and penetration vectors through adversarial security testing
37code-migration
Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools
35observability-logging
Use logs as part of comprehensive observability strategy including metrics, traces, alerts, and dashboards for system understanding and operational excellence
34white-hat
Build defensive security capabilities, implement security by design, and practice ethical hacking to protect systems proactively
34