forensics

To find the root cause of a GSD auto-mode crash, this Skill performs read-only analysis of runtime artifacts like activity logs and metrics to identify the failure point. It generates a citation-backed report referencing exact file paths and line numbers.

You can generate a GitHub-issue-ready bug report by running the forensics command after a failed run. It analyzes local artifacts, identifies the root cause, and outputs a structured issue report complete with cited evidence and fix suggestions.

The best way to analyze issue logs without modifying state is using a read-only forensics approach. This Skill inspects activity, journal, and metric artifacts to build a coherent cause chain while ensuring no state mutation occurs during diagnosis.

Yes, the forensics analysis saves a local copy of the root-cause report. Alongside delivering a GitHub-issue-ready output, it stores a permanent forensic record under the local .gsd/forensics directory for future auditing and reference.

You can use this for log analysis when a user needs read-only diagnosis of logs, activity, and metrics. It is designed to apply after running the forensics command or when an auto-mode crash occurs to identify root causes accurately.

A key limitation of this artifact analysis is its strict read-only constraint; it diagnoses issues without mutating any state. It relies entirely on existing .gsd runtime artifacts, meaning incomplete or missing logs will limit the accuracy of the root-cause report.