gsd-forensics
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
- License 许可
- MIT
- 最近更新
- 2026-08-01
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gsd-forensics
- description
- Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
03 SKILL.md 正文
<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> @~/.gemini/antigravity/gsd-core/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> Execute 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>
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zipai-optimizer
Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.