Bug Killer Debugger FAQs

Question 1

Does this skill support specific programming languages?

Accepted Answer

Yes, it includes specialized debugging references for Python and TypeScript/JavaScript, along with a robust general framework applicable to any programming language.

Question 2

Can I force the agent to perform a deeper investigation?

Accepted Answer

Yes, by using the --deep flag when invoking the skill, you can bypass the triage phase and move directly into a full-scale deep-track investigation.

Question 3

How does it ensure the fix doesn't break other features?

Accepted Answer

The 'Fix & Verify' phase requires running existing tests, performing a quality check, and writing a new regression test specifically designed to catch that bug in the future.

Question 4

What are the 'Quick' and 'Deep' tracks in the workflow?

Accepted Answer

The Quick track is for localized, obvious errors, while the Deep track is triggered for multi-file issues, intermittent bugs, or async problems, often using sub-agents for parallel investigation.

Question 5

How does Bug Killer differ from standard AI code fixing?

Accepted Answer

Standard AI often attempts to fix code immediately; Bug Killer enforces a 5-phase professional workflow that requires reproduction, evidence gathering, and hypothesis testing before any modifications are made.

Bug Killer Debugger

주요 기능

사용 사례

Bug Killer Debugger

주요 기능

사용 사례