gsd_forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
它会碰到什么
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
<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>
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。