skills.rest
GenproMM
GenproMMOFFICIAL
Explore all skills by this author →
GitHub

gsd-forensics

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

Updated Apr 3, 2026
Search Tags:#root cause analysis#git analysis#forensics#diagnostic report#GSD workflow
One-click install
npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-forensics-genpromm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/GenproMM/MMLab_TOOLS/tree/main/.claude/skills/gsd-forensics
Command: npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-forensics-genpromm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in diagnosing failures or stuck GSD workflows by analyzing git history, artifacts, and state, providing a structured diagnostic report to identify the root cause.

Core Features & Use Cases

  • Git History Analysis: Reviews git commits, patterns, and time gaps to detect anomalies.
  • Artifacts and State Review: Inspects .planning/ artifacts and file system state for in-depth analysis.
  • Structured Report Generation: Creates a forensic report detailing findings, anomalies, and recommendations.
  • Interactive Investigation: Offers interactive investigation for deeper analysis and optional issue creation in GitHub.
  • Use Case: When a GSD workflow fails or gets stuck, use this Skill to diagnose the issue, save time on troubleshooting, and take corrective action.

Quick Start

Analyze the cause of the failed GSD workflow by running the gsd-forensics skill with the problem description as an argument.

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 GSD workflow using git history analysis?▼

Diagnose a failed GSD workflow by analyzing git history, artifacts, and file system state. The tool reviews git commits, detects anomalies, and generates a structured forensic report with corrective actions.

Why does my GSD workflow get stuck during execution?▼

A GSD workflow gets stuck due to anomalies in git history or `.planning/` artifacts. Inspecting commit patterns, time gaps, and file system state reveals these common issues and identifies the root cause.

What is the best way to generate a diagnostic report for a stuck workflow?▼

The best way to generate a diagnostic report for a stuck workflow is running an analysis on git history and planning artifacts. This produces a structured forensic report detailing anomalies and recommendations.

Do I need access to specific planning files to run a git forensics analysis?▼

Yes, you need access to the git repository and specific workflow planning files. The analysis inspects `.planning/` artifacts and file system state to provide an in-depth diagnostic report.

Can I create a GitHub issue directly from a workflow forensics investigation?▼

Yes, you can create a GitHub issue directly from an interactive investigation. The analysis offers deeper inspection of failures and optionally creates issues to track the identified root cause.

What limitations exist when troubleshooting GSD workflows with git analysis?▼

Troubleshooting GSD workflows with git analysis is limited by the requirement for repository access and specific workflow planning files. Without these inputs, the forensic report cannot identify anomalies or suggest corrective actions.

Related Skills

Explore More Software Engineering Skills→
zcacereszcaceres
7

project-health

Analyze git state and configuration files to rate repository health from 0 to 10.

Community
Intermediate
connectwithprakashconnectwithprakash

GitHub Issue Fixer

Fix GitHub issues end-to-end from exploration to linked pull request creation.

Community
Advanced
roycolumbia-coderoycolumbia-code

gsd-forensics

Analyze GSD workflow failures by reviewing git history and .planning artifacts.

Community
Intermediate
hicucuhicucu
1

weekly-commits

Aggregate git commit history into structured markdown reports by timeframe and author.

Community
Intermediate