feat: /debug skill

Description

Cursor provides a debug mode that runs through a structured process to identify the root cause of a bug and fix it.

Requirements

The debug agent:

1. Prompts the user to describe the issue in detail, with any hypotheses they might have
2. Creates its own set of hypotheses as to what could cause the bug
3. Instruments the code with debugging logs to test the various hypotheses. Usually it sends the logs to a custom http server
4. Once that's done, it provides instructions to the user on how to reproduce the issue to test the hypotheses
5. After the use has reproduced the issue, you hit the "Proceed" button
6. Cursor reads the logs it captured
7. If it finds out that one of the hypotheses was correct, it puts a fix in place
8. Next, it gives you instructions to reproduce once more to confirm the fix
9. If the fix works, you can hit a "mark as fixed" button
10. At that time, it will remove all debugging code leaving the fix in place.

In the end, it provides a very structured way to narrow down bugs in a structured, interactive way. I actually still use this quite regularly over Claude Code when debugging an issue because I find the flow directs me to the root cause of the bug, even using the Composer 2 model which is not as good as Opus!

Additional Context

No response