skills.rest
hadpadrahul
hadpadrahulCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

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

Updated Apr 22, 2026
Search Tags:#git#workflow#diagnostics#forensics#anomaly#gsd
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-forensics-hadpadrahul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-forensics
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-forensics-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose failed or stuck GSD workflow executions by analyzing git history, artifacts, and filesystem state.

Core Features & Use Cases

  • Collects and correlates recent commits, repository state, and planning artifacts to surface root causes.
  • Generates structured forensic reports saved to .planning/forensics/ that summarize anomalies and recommended actions.
  • Provides an interactive investigation flow that can surface issues across multiple data sources (git, planning state, session history).

Quick Start

Run the forensics workflow on the current GSD session and review the generated report at .planning/forensics/.

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 git workflow execution in my repository?▼

To diagnose a failed git workflow execution, you can analyze recent commits, planning artifacts, and filesystem state to surface root causes and generate a structured forensic report saved to .planning/forensics/.

What is post-mortem forensics for stuck GSD workflows?▼

Post-mortem forensics for stuck GSD workflows is the process of aggregating git logs, planning state, and session data to investigate anomalies and identify why a workflow execution halted.

How do I generate a forensic report from git history and planning artifacts?▼

You generate a forensic report by running an interactive investigation flow that collects and correlates git history, planning artifacts, and session state, saving the structured report directly to .planning/forensics/.

Does workflow diagnostics work without external dependencies?▼

Yes, workflow diagnostics works without external dependencies because the Skill requires no dependencies to analyze git history, filesystem state, and planning artifacts for post-mortem investigations.

Why does my GSD workflow fail to find anomalies in the session state?▼

Your GSD workflow may fail to find anomalies if the session state, recent commits, or planning artifacts lack sufficient correlation data to surface root causes during the interactive investigation flow.

What's the best way to investigate root causes of failed GSD sessions?▼

The best way to investigate root causes of failed GSD sessions is to correlate repository state with planning artifacts and git history to produce evidence-based diagnostics and recommended actions.

Related Skills

Explore More Software Engineering Skills→
D0NMEGAD0NMEGA
8

gsd-forensics

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

Community
Advanced
GenproMMGenproMM

gsd-forensics

Analyze git history, artifacts, and state to diagnose failed GSD workflows.

Official
Advanced
coco-researchcoco-research
264

gsd-forensics

Analyze git history and planning artifacts to diagnose failed GSD workflows.

Community
Advanced
gesmith0606gesmith0606

gsd-forensics

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

Community
Advanced