Open
Conversation
…problem is and jump straight to implementation. Sometimes it will be wrong. It can take a lot of back and forth, and for each hypothesis Claude will make changes to the code that it won't undo after it eventually gets the solution right. /bugfix forces a disciplined workflow: reproduce the bug first, prove the root cause before writing any code, then fix it with a failing test as proof. No guessing, no leftover changes from wrong attempts. And after the fix, it closes the test gap that let the bug through in the first place.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When you present Claude Code with a bug, it tends to assume what the problem is and jump straight to implementation. Sometimes it will be wrong. It can take a lot of back and forth, and for each hypothesis Claude will make changes to the code that it won't undo after it eventually gets the solution right.
The new /bugfix skill forces a disciplined workflow: reproduce the bug first, prove the root cause before writing any code, then fix it with a failing test as proof. No guessing, no leftover changes from wrong attempts. And after the fix, it closes the test gap that let the bug through in the first place.