Systematic Bug Fixer FAQs

Question 1

Does this skill update my project documentation?

Accepted Answer

Yes, after a fix is implemented, it initiates a 'trace' phase that records the fix in your changelog and prepares code mapping changes for your architectural documents.

Question 2

Can I use the debug skill without design documents?

Accepted Answer

Yes, the skill includes a 'General Debug' mode for when spec.md or arch.md are unavailable, though it is most effective when it can cross-reference your intended design.

Question 3

Which Claude model is recommended for debugging?

Accepted Answer

Claude 3.5 Sonnet is the default choice for most bugs, but Claude 3 Opus is highly recommended for complex issues involving multi-file analysis and deep flow logic.

Question 4

How does the skill verify that a bug is actually fixed?

Accepted Answer

It uses the Shell tool to execute your project's specific run commands (like npm run dev or uvicorn), performing a live verification check in the E2E environment.

Question 5

What is the difference between /test and /debug in this skill?

Accepted Answer

Use /test for fixing specific unit test failures. Use /debug for E2E issues where functionality is broken even if unit tests are passing, such as integration or environment-specific bugs.

Systematic Bug Fixer

Key Features

Use Cases

Systematic Bug Fixer

Key Features

Use Cases