skills.rest
nnexai
nnexaiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Audit git state, planning artifacts, and session logs to generate forensic reports for failed GSD workflows.

1|Updated Apr 4, 2026
Search Tags:#automation#git#workflow#debugging#diagnostic#forensics
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-forensics-nnexai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-forensics
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-forensics-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured post-mortem analysis for failed or stuck GSD (Git-Stacks-Development) workflows, identifying root causes like abandoned tasks, missing artifacts, or interrupted processes.

Core Features & Use Cases

  • Anomaly Detection: Automatically scans git history, session state, and planning artifacts to detect stuck loops or missing files.
  • Forensic Reporting: Generates a detailed diagnostic report in the .planning/forensics/ directory.
  • Use Case: When a complex multi-agent workflow hangs or fails to produce expected output, use this Skill to audit the session state and receive actionable recommendations for recovery.

Quick Start

Invoke the gsd-forensics skill to analyze the current project state and generate a diagnostic report for the most recent failed workflow.

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 in a multi-agent environment?▼

Diagnosing a failed git workflow involves auditing git state, planning artifacts, and session logs to identify anomalies like stuck loops or interrupted task sequences. This generates a structured forensic report detailing the root cause.

What causes a multi-agent development workflow to get stuck in a loop?▼

A multi-agent workflow gets stuck in loops due to abandoned tasks, missing planning artifacts, or interrupted processes. Auditing git history and session state detects these anomalies and identifies the exact interruption point.

How do I generate a diagnostic report for an interrupted GSD workflow?▼

To generate a diagnostic report for an interrupted workflow, analyze the .planning directory and git repository metadata using read-only access. The system outputs a detailed forensic report directly into the .planning/forensics/ directory.

Does the forensic analysis require write access to the git repository?▼

No, forensic analysis requires only read-only access to the .planning directory and git repository metadata. This ensures the diagnostic process safely audits the session state without modifying the existing repository files.

What is the best way to debug missing planning artifacts in automated development?▼

The best way to debug missing planning artifacts is to run an anomaly detection scan across git history and session state. This identifies missing files and generates actionable recommendations for recovering the failed workflow.

Related Skills

Explore More Software Engineering Skills→
MINT-IAMINT-IA

gsd-forensics

Diagnose failed GSD workflow executions and generate evidence-backed forensic reports.

Official
Advanced
gesmith0606gesmith0606

gsd-forensics

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

Community
Advanced
vladm3105vladm3105
16

n8n

Design n8n workflows, custom nodes, and integrations across services.

Community
Advanced
aslaiiaslaii

gsd-forensics

Analyze git history and planning artifacts to diagnose GSD workflow failures.

Community
Advanced