Diagnose failed GSD workflow executions and generate evidence-backed forensic reports.
npx skills add https://github.com/MINT-IA/MINT --skill gsd-forensics-mint-ia
Please help me install this Agent Skill. Skill: gsd-forensics Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-forensics Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-forensics-mint-ia
This Skill helps teams diagnose why a Get-Shit-Done (GSD) workflow failed or got stuck by analyzing git history, .planning artifacts, and filesystem state to produce evidence-backed findings and actionable recommendations.
Ask the gsd-forensics skill to investigate the most recent failed GSD workflow and write a forensic report to .planning/forensics/.
High-intent search queries and answers about installing and using this skill.
To diagnose a failed git workflow halted mid-phase, analyze git history and planning artifacts to detect stuck loops, missing artifacts, or uncommitted changes. The tool collects logs and diffs to produce an evidence-backed forensic report identifying the failure cause.
Investigating abandoned work and inconsistent state transitions requires inspecting git history and planning state files. This skill cross-references commits with phase artifacts to detect anomalies, citing specific commits and files for every finding in a structured report.
Yes, you can run incident response forensics with read-only access to git data and the .planning directory. The process gathers evidence and writes a timestamped forensic report to .planning/forensics/ without modifying any source files.
Automated workflows get stuck in loops due to inconsistent state transitions, missing verification artifacts, or recent commits introducing failures. Analyzing git diffs and planning state files identifies the exact commit or uncommitted change causing the loop.
Yes, generating a forensic postmortem report requires a .planning directory containing state files like STATE.md, ROADMAP.md, and phase PLAN.md, SUMMARY.md, and VERIFICATION.md files. The analysis correlates these planning artifacts with git history to produce evidence-backed findings.
Git history forensics for crash or interruption analysis is limited to evidence available in commits, diffs, and .planning artifacts. It cannot diagnose failures caused by external system crashes or environmental issues if those events left no trace in the repository's git data or planning files.
deerawanExtracts decisions, lessons, patterns, and surprises from phase artifacts into a LEARNINGS.md document.
gesmith0606Diagnose failed GSD workflows by analyzing git history and .planning artifacts.
Pear-CommerceCapture ideas, tasks, and issues as structured todo items during GSD workflows.
JetXu-LLMTrace knowledge objects to evidence units and provenance records.
