debug-issue

To find the root cause of a production incident, this skill analyzes timeline debug metadata to correlate browser and backend events, isolating the earliest failing signal. It delegates to an issue-forensics subagent to pinpoint the first anomaly and generate a structured hypothesis.

To triage chat sync or encryption issues, the skill runs debug timeline forensics and optionally triggers an encryption-flow-tracer pass. This localizes broken invariants and returns a structured JSON output containing the root cause hypothesis and suspect files.

Yes, you can identify suspect files and recent commits without manual git blame because the skill automates issue triage. It returns structured JSON containing suspect files, relevant reproduction steps, and recent related commits to guide your fix.

The best way to implement a minimal corrective patch is to use the structured JSON output from the issue triage. You apply fixes to the identified suspect files based on the root cause hypothesis, then confirm the fix with the provided debug cleanup command.

Yes, issue triage works with both frontend and backend event correlation. The investigation process correlates browser and backend events from timeline debug metadata to isolate the earliest failing signal across general backend and frontend symptom patterns.