gsd-forensics

To diagnose a failed git workflow and generate a post-mortem report, you analyze git history and .planning artifacts to collect evidence, detect anomalies like stuck loops, and write structured remediation findings to .planning/forensics/.

A git workflow can get stuck or crash due to uncommitted or conflicting work, missing or abandoned phase artifacts, or interruption indicators. Forensic diagnostics identify these specific anomalies by citing concrete commits and file states from the working tree.

You investigate uncommitted changes and missing artifacts by running a forensic analysis that checks git status, git diff, and .planning/STATE.md. The process classifies abandoned artifacts and grounds findings in concrete evidence for actionable remediation.

Forensic report generation does not require write access to source files. It strictly handles source files as read-only, requiring only permission to write the structured forensic report into the .planning/forensics/ directory while redacting sensitive data.

You can automatically create a GitHub issue from workflow diagnostics findings. After generating the forensic report with actionable recommendations, the Skill optionally proposes creating a GitHub issue to track the identified remediation items.

The best way to triage crashed workflow executions is to perform evidence-backed forensic diagnostics on repositories containing git history and .planning artifacts. This collects recent session reports and classifies crash indicators to present inline remediation recommendations.