Analyze git history and artifacts to document failed GSD workflow root causes.
npx skills add https://github.com/onelee85/my-skills --skill gsd-forensics
Please help me install this Agent Skill. Skill: gsd-forensics Source: https://github.com/onelee85/my-skills/tree/main/gsd-forensics Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong.
Run the forensics workflow to generate a diagnostic report from the current project state.
High-intent search queries and answers about installing and using this skill.
To investigate a failed GSD workflow, this Skill analyzes git history, planning artifacts, and workspace state to identify root causes. It gathers evidence and generates a structured forensic report to restore workflow health.
The best way to run a post-mortem for stalled GSD runs is using an interactive investigation workflow that analyzes commits and file-system state. It redacts sensitive data and writes actionable findings to a dedicated forensics directory without modifying source files.
No, the forensic analysis does not modify your source files. It safely gathers evidence, redacts sensitive data, and writes the structured diagnostic report exclusively to the .planning/forensics/ directory.
Yes, you can create issues from actionable findings. The interactive investigation workflow includes optional issue creation to help restore workflow health based on the structured root-cause analysis of your failed GSD runs.
Diagnosing failed GSD workflows requires analyzing git history, planning artifacts, and workspace file-system state. The Skill gathers evidence from these multiple data sources to identify the root causes of failed or stalled runs.
D0NMEGAAnalyze git history and planning artifacts to identify root causes of failed GSD workflows.
DaBigHomieCreate ITSM Problem Records from incident reports with root causes and remediation plans.
IdanDavidAvivAutomates software release governance with strict versioning, changelog and artifact checks.
koki3141Structure claims, generate hypotheses, and collect evidence for root cause analysis.
