skills.rest
Poom5741
Poom5741COMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Diagnose failed GSD workflows by analyzing git history, artifacts, and state.

Updated Mar 15, 2026
Search Tags:#diagnostics#workflows#forensics#git-history#state-tracking#artifact-analysis#gsd
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-forensics-poom5741
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-forensics
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-forensics-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Analyzes recent git history to identify anomalies and timing gaps
  • Assesses .planning/ artifacts and STATE/ROADMAP data to reconstruct session history
  • Generates a structured forensic report saved to .planning/forensics/ and highlights actionable findings

Quick Start

Run the forensic workflow to generate a diagnostic report for the current GSD session.

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 stalled or failed GSD workflow session?▼

Post-mortem analysis for failed GSD workflows reconstructs session history by examining git history, .planning artifacts, and STATE/ROADMAP data. It detects anomalies like stuck loops, missing artifacts, and crashes to identify exactly what went wrong.

What is the best way to find missing artifacts in git history after a crash?▼

The best way to find missing artifacts is to audit git history and .planning/ state data together. A forensic post-mortem detects anomalies such as missing artifacts, abandoned work, and crashes, then highlights actionable findings in a structured report.

Do I need access to .planning artifacts to run a state-tracking forensic analysis?▼

Yes, forensic analysis requires access to .planning artifacts and STATE/ROADMAP data across repositories, branches, and sessions. These sources are audited to reconstruct session history and detect anomalies like stuck loops or crashes.

How does forensic artifact analysis work for abandoned work in repositories?▼

Forensic artifact analysis audits multiple data sources across repositories, branches, and sessions to detect anomalies like abandoned work. It cross-references git history with .planning artifacts and STATE data to reconstruct session timelines.

Where are structured forensic reports saved when diagnosing GSD workflow failures?▼

Structured forensic reports are saved under the .planning/forensics/ directory. This report highlights actionable findings derived from analyzing git history, artifacts, and state-tracking data to diagnose failed GSD runs.

Related Skills

Explore More Data & Analytics Skills→
D0NMEGAD0NMEGA
8

gsd-forensics

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

Community
Advanced
jedmamostojedmamosto

gsd-forensics

Diagnose failed GSD workflow executions by analyzing git history and `.planning/` artifacts.

Community
Advanced
ThiagoVitaleThiagoVitale

gsd-forensics

Diagnose failed GSD workflows by analyzing git history and .planning artifacts.

Community
Advanced
YukiIto1999YukiIto1999

analyzing-windows-lnk-files-for-artifacts

Extract forensic artifacts from Windows LNK shortcut files.

Community
Advanced