Analyze session debugging data to identify errors and issues that may have caused a user-reported problem.
Analyze session debugging data to identify errors and issues that may have caused a user-reported problem.
$ARGUMENTS: Two space-separated arguments expected:
http:// or https://)Parse and validate the arguments:
Split $ARGUMENTS on whitespace to get exactly two arguments:
http:// or https://)123 or full URL like https://github.com/owner/repo/issues/123)Validation: If fewer than two arguments are provided, inform the user:
"Usage: /dyad:session-debug <session-data-url> <issue-number-or-url>" "Example: /dyad:session-debug https://example.com/session.json 123"
Then stop execution.
Fetch the GitHub issue:
gh issue view <issue-number> --json title,body,comments,labels
Understand:
Fetch the session debugging data:
Use WebFetch to retrieve the JSON session data from the provided URL.
Analyze the session data:
Look for suspicious entries including:
Correlate with the reported issue:
For each suspicious entry found, assess:
Rank the findings:
Create a ranked list of potential causes, ordered by likelihood:
## Most Likely Causes
### 1. [Error/Issue Name]
- **Evidence**: What was found in the session data
- **Timestamp**: When it occurred
- **Correlation**: How it relates to the reported issue
- **Confidence**: High/Medium/Low
### 2. [Error/Issue Name]
...
Provide recommendations:
For each high-confidence finding, suggest:
Summarize: