gsd-forensics

Name: gsd-forensics
Availability: InStock
Author: rkz91

Analyze git history, planning artifacts, and session state to identify root causes of failed GSD workflows.

264|11|Updated Apr 25, 2026

Search Tags:#git #artifacts #diagnose #workflows #forensics #gsd

Ready to run

npx skills add https://github.com/rkz91/coco --skill gsd-forensics-rkz91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-forensics
Command: npx skills add https://github.com/rkz91/coco --skill gsd-forensics-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem diagnostics for failed GSD workflows help identify root causes by analyzing git history, planning artifacts, and current state to surface actionable insights.

Core Features & Use Cases

Forensic analysis across commits, artifacts, and session state to generate an actionable report.
Detect common failure modes such as stuck phases, missing artifacts, or inconsistent state.
Use Case: When a GSD execution stalls, run the forensics workflow to produce a structured report and remediation guidance.

Quick Start

Run the forensics workflow on the failing GSD session to generate a diagnostic report.

Frequently Asked Questions about gsd-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose a failed or stalled GSD workflow using git history?▼

Diagnose failed GSD workflows by running the forensics workflow, which examines git history, planning artifacts, and session state to identify root causes and generate a structured report.

What is post-mortem forensic analysis for failed software engineering workflows?▼

Post-mortem forensics is a diagnostic process that analyzes git commits, planning artifacts, and session state to detect common failure modes like stuck phases or missing artifacts, producing actionable remediation guidance.

Can I detect inconsistent state and missing artifacts in a stalled GSD execution?▼

Yes, forensics detects common failure modes such as stuck phases, missing artifacts, and inconsistent state by analyzing current session data and planning artifacts across projects and teams.

How do I generate a forensic report for a failed git workflow execution?▼

Generate a forensic report by running the diagnostics workflow on the failing session, which performs data-gathering and anomaly detection to produce written analysis with optional issue creation.

Do I need any dependencies to run forensics on failed GSD workflows?▼

No dependencies are required, allowing the forensics workflow to directly examine git history and current session state to surface actionable insights without additional environment setup.