skills.rest
ArtRiv
ArtRivCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Diagnose GSD workflow failures using git history and planning artifacts.

Updated Feb 11, 2026
Search Tags:#debugging#github issues#git history#planning artifacts#incident diagnosis#workflow forensics
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-forensics-artriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-forensics
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-forensics-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand why a GSD workflow failed or got stuck by collecting concrete evidence from git history and the repository’s planning artifacts, then summarizing what likely happened without guessing.

Core Features & Use Cases

  • Evidence-based failure diagnosis: Reviews git log, git status/git diff, and .planning/* state to find anomalies tied to specific commits and files.
  • Structured forensic reporting: Produces a timestamped report under .planning/forensics/ with findings, anomaly categories, and recommendations.
  • Actionable next steps: Offers interactive deep-dive and suggests GitHub issue creation when findings indicate what to fix.

Use Case: A workflow stops mid-phase or repeatedly re-runs; you run this Skill to determine whether artifacts are missing, work was abandoned, a crash/interruption occurred, or a loop got stuck—then you get a clear report you can share with the team.

Quick Start

Run the gsd-forensics skill and provide a short problem description of the failed or stuck workflow execution so it can generate an evidence-backed report in .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 workflow execution using git history and planning artifacts?▼

Workflow forensics examines git history and .planning/ artifacts to identify why a run fails, loops, crashes, or leaves incomplete artifacts across planning phases. It checks multiple anomaly types to determine exactly what happened during the execution.

How do I find out why my GSD workflow stopped mid-phase or keeps re-running?▼

Run a forensic diagnosis providing a short problem description of the failed or stuck workflow execution. The tool reads git history and .planning/ state, checks multiple anomaly types, and writes a redacted forensic report to .planning/forensics/ without modifying source files.

Does the forensic diagnosis modify my source files when checking for workflow anomalies?▼

No, the forensic diagnosis does not modify source files. It strictly reads git history and .planning/ state to generate a redacted forensic report under .planning/forensics/, ensuring your repository's source code remains untouched during the anomaly investigation.

Can I create a GitHub issue directly from the workflow forensics report findings?▼

Yes, you can create a GitHub issue from the forensic report. When the evidence-based diagnosis identifies what to fix, it suggests GitHub issue creation and offers an interactive deep-dive to help your team track and resolve the workflow failure.

What types of workflow anomalies can be detected by checking git history and planning state?▼

Checking git history and .planning/ state detects missing artifacts, abandoned work, crash or interruption events, and stuck loops. These anomalies are tied to specific commits and files across .planning/ phases and reports, providing concrete evidence of what went wrong.

Related Skills

Explore More Software Engineering Skills→
jedmamostojedmamosto

gsd-forensics

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

Community
Advanced
GenproMMGenproMM

gsd-forensics

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

Official
Advanced
tinner-deinnotinner-deinno

gsd-forensics

Diagnose failed GSD workflows by reconstructing execution history from git logs and .planning artifacts.

Community
Intermediate
yusaduymazyusaduymaz

gsd-forensics

Diagnose failed GSD workflow runs by tracing root causes in git history and artifacts.

Community
Advanced