Ask Bug Finder
Systematic debugging with reproduction, isolation, and hypothesis testing.
Ask Bug Finder by NavanithanS · 7cb2d52
npx skillmds@latest add navanithans/ask-bug-finder File contents
---name: ask-bug-finderdescription: Systematic debugging with reproduction, isolation, and hypothesis testing.---<critical_constraints>❌ NO fixing without reproducing first❌ NO changing random things hoping it works❌ NO fixing symptoms instead of root cause✅ MUST read full error message including stack trace✅ MUST form hypothesis before making changes✅ MUST write test after fixing to prevent recurrence</critical_constraints><process>1. **Reproduce**: - Ensure consistent steps. - Compare expected vs actual. - Check all environments.2. **Gather**: - Collect error messages and logs. - Review recent changes. - Check environment details.3. **Hypothesize**: - Identify suspect components. - Seek simplest explanation.4. **Test**: - Add strategic logging. - detailed assertions. - Comment out sections.5. **Fix**: - Make minimal changes. - Verify fix. - Check regressions. - Add test case.</process><techniques>- **Binary Search**: git bisect to find breaking commit- **Rubber Duck**: explain problem aloud, bug reveals itself- **Divide & Conquer**: midpoint check, narrow scope- **Print Debug**: `[DEBUG] func_name: var={var}` (not just "here")</techniques><common_patterns>- Off-by-one: `range(len(x)-1)` → should be `range(len(x))`- Null reference: `user.name` without checking `user is None`- Race condition: check-then-act pattern- State mutation: `items.sort()` modifies original</common_patterns><tools>| Tool | Use ||------|-----|| Debugger (pdb) | step through, inspect || Logger | track execution flow || Profiler | performance issues || git bisect | find breaking commit |</tools><when_stuck>1. Take a break2. Explain to someone (rubber duck)3. Check the obvious (is server running?)4. Search for similar issues5. Create minimal reproduction</when_stuck>
NavanithanS/Agent-Skill-Kit/tree/main/skills/coding/ask-bug-finder commit 7cb2d5276c
Frequently asked questions
Run npx skillmds@latest add navanithans/ask-bug-finder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Systematic debugging with reproduction, isolation, and hypothesis testing. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
NavanithanS (@navanithans) published this skill. Their other Agent Skills are listed on their SkillMD profile.