Skip to main content

gsd-forensics

Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.

Quellinformationen

Repository
coco-research/coco
Letzte Quellaktivität
14. September 2026 um 16:24
Erkannte Sprache von SKILL.md
Englisch
Sterne
634
Forks
12

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
gsd-forensics
description
Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.
argument-hint
[problem description]
allowed-tools
["Read","Write","Bash","Grep","Glob"]
<objective> Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report. Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation. </objective> <execution_context> @$HOME/.claude/get-shit-done/workflows/forensics.md </execution_context> <context> **Data sources:** - `git log` (recent commits, patterns, time gaps) - `git status` / `git diff` (uncommitted work, conflicts) - `.planning/STATE.md` (current position, session history) - `.planning/ROADMAP.md` (phase scope and progress) - `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md) - `.planning/reports/SESSION_REPORT.md` (last session outcomes) **User input:** - Problem description: $ARGUMENTS (optional — will ask if not provided) </context> <process> Read and execute the forensics workflow from @$HOME/.claude/get-shit-done/workflows/forensics.md end-to-end. </process> <success_criteria> - Evidence gathered from all available data sources - At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption) - Structured forensic report written to `.planning/forensics/report-{timestamp}.md` - Report presented inline with findings, anomalies, and recommendations - Interactive investigation offered for deeper analysis - GitHub issue creation offered if actionable findings exist </success_criteria> <critical_rules> - **Read-only investigation:** Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking. - **Redact sensitive data:** Strip absolute paths, API keys, tokens from reports and issues. - **Ground findings in evidence:** Every anomaly must cite specific commits, files, or state data. - **No speculation without evidence:** If data is insufficient, say so — do not fabricate root causes. </critical_rules>
Auf GitHub ansehen