Add /analyze-crash and /analyze-error Claude commands #7961
+496
−0
Conversation
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
bouwkast
added
the
AI Generated
lucaspimentel
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of changes
When investigating crashes or errors a main difficulty (in my opinion) is both the volume of them 😭 but also unfamiliarity of the various frames in the stacks. This PR adds two (experimental) Claude Code commands to assist with this
/analyze-crashand/analyze-error.Reason for change
As I have been going through stacks and frames from Crash Tracking I found myself constantly having to look up what things mean as I'm just not super familiar with most of the native bits at the moment. These two commands are largely created to help me speed up initial understanding and analysis of stacks from reported crashes that are (likely) caused by
dd-trace-dotnet.In addition to this, it made some sense to include a similar command for errors (that are not crashes, but are caused by us).
The analysis documents are intended to help de-mystify both and provide more human readable information.
Implementation details
Both commands will output a markdown file within your user
.claude\analysis\directory (creates it if necessary).Test coverage
Other details
I would consider these experimental and will continue to test them out.
To use:
Intention is to click the
Copystack button in Error Tracking and then paste it into the command. That is it!