Skip to main content

gsd-forensics

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

来源信息

仓库
davepoon/buildwithclaude
最近来源活动
2026年5月9日 09:12
检测到的 SKILL.md 语言
英语
星标
3,639
分支
605

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
type
prompt
name
gsd:forensics
description
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
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> @${CLAUDE_PLUGIN_ROOT}/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 @${CLAUDE_PLUGIN_ROOT}/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>
在 GitHub 查看