skills.rest
ThiagoVitale
ThiagoVitaleCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

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

Updated May 3, 2026
Search Tags:#git#workflow#diagnosis#forensics#GSD
One-click install
npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-forensics-thiagovitale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-forensics
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-forensics-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose what went wrong during failed GSD (Get Shit Done) workflows, enabling users to understand the root cause and take corrective action.

Core Features & Use Cases

  • Post-mortem Investigation: Analyzes git history, .planning artifacts, and file system state to detect anomalies.
  • Structured Diagnostic Report: Generates a report with findings, anomalies, and recommendations.
  • Interactive Investigation: Offers deeper analysis for complex issues.
  • GitHub Issue Creation: Optionally creates an issue with actionable findings.

Quick Start

Invoke the gsd-forensics skill to diagnose a failed workflow by mentioning $gsd-forensics followed by the problem description.

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 and find the root cause?▼

To diagnose a failed git workflow, you can analyze git history, .planning artifacts, and file system state to detect anomalies. This generates a structured diagnostic report with findings and recommendations.

What is the best way to investigate post-mortem issues in failed development workflows?▼

Investigating post-mortem issues involves analyzing git history and file system state to uncover anomalies. A structured diagnostic report provides actionable findings and recommendations for corrective action.

How do I analyze .planning artifacts to troubleshoot workflow failures?▼

You can analyze .planning artifacts alongside git history and file system state to troubleshoot workflow failures. This process detects anomalies and generates a diagnostic report with recommendations.

Can I automatically create a GitHub issue from a git workflow diagnostic report?▼

Yes, you can automatically create a GitHub issue containing actionable findings from a workflow diagnostic report. This option is available after analyzing git history and .planning artifacts.

Do I need access to git repositories to run a workflow forensics diagnosis?▼

Yes, you need access to git repositories and .planning directories to run a workflow forensics diagnosis. The analysis relies on examining git history, artifacts, and file system state.

Why does my GSD workflow failure require interactive investigation?▼

Complex GSD workflow failures may require interactive investigation to perform deeper analysis. This helps uncover intricate anomalies in git history and .planning artifacts that standard checks might miss.

Related Skills

Explore More Software Engineering Skills→
dobrinz123dobrinz123

gsd-forensics

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

Community
Advanced
RangeyRoverRangeyRover
3

speckit.taskstoissues

Convert technical tasks into GitHub issues with dependency ordering.

Community
Intermediate
jedmamostojedmamosto

gsd-forensics

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

Community
Advanced
0xHoneyJar0xHoneyJar

detecting-staleness

Compute confidence-based freshness scores from frontmatter, git history, and configuration.

Official
Advanced