Analyze GSD runtime artifacts to produce a GitHub-issue-ready forensic report.
npx skills add https://github.com/qdzsh/gsd-revamp --skill forensics-qdzsh
Please help me install this Agent Skill. Skill: forensics Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/forensics Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill forensics-qdzsh
Post-mortem a failed GSD auto-mode run. Traces from symptom to root cause using .gsd/activity/*.jsonl, .gsd/journal/YYYY-MM-DD.jsonl, .gsd/metrics.json, and .gsd/auto.lock. Produces a filing-ready bug report with file:line references and a concrete fix suggestion. Reads existing artifacts — does NOT re-run anything.
Run /gsd forensics to generate a deeper forensic report from the current session artifacts.
High-intent search queries and answers about installing and using this skill.
To investigate a failed auto-mode run, you can trace symptoms to root causes by analyzing read-only runtime artifacts in .gsd/activity, .gsd/journal, and .gsd/metrics.json. This generates a GitHub-issue-ready forensic report with exact file:line citations.
The best way to generate a post-mortem report for an unexpected session termination is to analyze .gsd/auto.lock and journal artifacts. This read-only process identifies the root cause and outputs a structured narrative with a concrete fix suggestion without mutating state.
Yes, you can find the root cause of a unit re-dispatch loop without re-running anything. Forensic analysis reads existing JSONL traces and metrics to map the failure progression, providing a remediation plan based solely on historical runtime data.
No, forensic analysis of GSD artifacts does not modify your project state. The investigation is strictly read-only, parsing existing activity logs and metrics to produce a filing-ready bug report without executing or mutating any code.
You need to analyze .gsd/journal and .gsd/metrics.json files when auto-mode fails, a session ends unexpectedly, or a unit loops. These artifacts provide the runtime traces required to identify root causes for a formal post-mortem investigation.
A forensic report produced from runtime traces includes a GitHub-issue-ready narrative, exact citations to artifact paths and lines, and a concrete fix suggestion. It maps the failure from symptom to root cause using read-only activity logs.
open-gsdAnalyze GSD runtime artifacts to identify auto-mode failure root causes.
RomualdPIdentify bug root causes through a six-step diagnostic workflow.
vh2224Diagnose GSD auto-mode failures by inspecting .gsd/ runtime artifacts.
Miosa-osaAnalyze LLM execution traces to categorize failures and generate an error taxonomy.
