Agent Skills
› AjayIrkal23/agentic-mercy-10x
› gsd-forensics
gsd-forensics
GitHub针对GSD工作流失败或卡死进行事后调查，通过分析git历史、规划工件及文件系统状态来诊断异常并生成结构化报告，帮助用户定位根因。
Trigger Scenarios
工作流执行失败
工作流卡住无响应
需要排查任务中断原因
Install
npx skills add AjayIrkal23/agentic-mercy-10x --skill gsd-forensics -g -y
SKILL.md
Frontmatter
{
"name": "gsd-forensics",
"description": "Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.",
"allowed-tools": [
"Read",
"Write",
"Bash",
"Grep",
"Glob"
],
"argument-hint": "[problem description]"
}
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> @$HOME/.claude/get-shit-done/workflows/forensics.md </execution_context>
User input:
- Problem description: $ARGUMENTS (optional — will ask if not provided)
<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>
Version History
- 581d130 Current 2026-07-19 09:09
