forensics

Diagnose GSD auto-mode failures by inspecting .gsd/ runtime artifacts.

1|Updated Jul 13, 2026

Search Tags:#debugging #root cause #logs #post-mortem #forensics #gsd #stuck loop

Ready to run

npx skills add https://github.com/vh2224/forge-executor --skill forensics-vh2224

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: forensics
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/forensics
Command: npx skills add https://github.com/vh2224/forge-executor --skill forensics-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you investigate why a GSD auto-mode run failed, stalled, or ended unexpectedly by turning runtime artifacts into a clear, evidence-backed root cause analysis.

Core Features & Use Cases

Artifact analysis: Reads .gsd/ logs, journals, metrics, locks, and paused-session state to reconstruct what happened.
Root-cause tracing: Links symptoms to the exact file, line, or event that likely caused the failure.
Issue-ready reporting: Produces a concise report with evidence, proposed fix, and test ideas for filing or sharing.
Use case: A loop keeps re-dispatching the same unit, a stale lock remains after a crash, or auto-mode stops without explanation.

Quick Start

Ask for a read-only forensic investigation of the latest GSD failure and request a GitHub-issue-ready report with cited evidence and a proposed fix.

Frequently Asked Questions about forensics

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

FAQPage Schema

How do I debug a GSD auto-mode run that stalled or stopped unexpectedly?▼

To debug a stalled GSD auto-mode run, perform a read-only forensic investigation of `.gsd/` runtime artifacts like activity logs, journals, metrics, and paused-session files to pinpoint the root cause.

Why does my GSD workflow keep re-dispatching the same unit in a stuck loop?▼

A stuck re-dispatch loop is caused by unresolved state or event conflicts recorded in `.gsd/` journals and metrics. Analyzing these runtime artifacts traces the repeated dispatch back to its originating file and line.

What is the best way to find the root cause of a stale lock after a crash?▼

The best way to find a stale lock's root cause is inspecting `.gsd/` lock files and paused-session state. This read-only analysis links the lingering lock to the specific crash event and line reference.

Can I generate a GitHub-issue-ready post-mortem report from GSD logs?▼

Yes, you can generate an issue-ready post-mortem report from GSD logs. The analysis produces a concise report containing cited evidence with file and line references, a proposed fix, and test ideas.

Does forensics analysis modify my paused-session files during root cause tracing?▼

No, forensics analysis does not modify paused-session files. It requires strictly read-only inspection of `.gsd/` state, ensuring your original runtime artifacts remain untouched during root cause tracing.