get-shit-done/commands/gsd/forensics.md at main

mirror of https://github.com/glittercowboy/get-shit-done synced 2026-04-25 17:25:23 +02:00

Files

Tom Boucher ee219e7726 fix: address review findings on forensics PR #1305

1. Resolve read-only contradiction: critical_rules now explicitly allows
   STATE.md session tracking alongside the forensic report write
2. Add label existence check before gh issue create --label "bug" to
   handle repos without a "bug" label gracefully

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-21 18:21:41 -04:00

2.3 KiB

Raw Permalink Blame History

type, name, description, argument-hint, allowed-tools

type

name

description

argument-hint

allowed-tools

prompt

gsd:forensics

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

[problem description]

Read

Write

Bash

Grep

Glob

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.

<execution_context> @~/.claude/get-shit-done/workflows/forensics.md </execution_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)

Read and execute the forensics workflow from @~/.claude/get-shit-done/workflows/forensics.md end-to-end.

<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>

2.3 KiB Raw Permalink Blame History

2.3 KiB

Raw Permalink Blame History