skills.rest
roycolumbia-code
roycolumbia-codeCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

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

Updated Mar 23, 2026
Search Tags:#workflow analysis#diagnostic reporting#GSD workflow#workflow troubleshooting#git forensics
One-click install
npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-forensics-roycolumbia-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/roycolumbia-code/claude-global-config/tree/main/skills/_audit-disabled-20260706-1136/gsd-forensics
Command: npx skills add https://github.com/roycolumbia-code/claude-global-config --skill gsd-forensics-roycolumbia-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The gsd-forensics Skill solves the problem of identifying and diagnosing the root cause of failed or stuck GSD workflows.

Core Features & Use Cases

  • Workflow Diagnostics: Analyzes git history and workflow artifacts to diagnose issues.
  • Interactive Reporting: Generates a structured diagnostic report that can be presented inline.
  • Actionable Insights: Offers insights to correct failed workflows and create GitHub issues if necessary.

Quick Start

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

To diagnose GSD workflow failures, you can analyze your git history and .planning artifacts to identify the root cause of stuck or failed workflows. This process reviews workflow-specific files to generate actionable diagnostic reports.

What is a GSD workflow troubleshooting process and when do I need it?▼

GSD workflow troubleshooting is the process of reviewing git history and workflow artifacts to identify why a process failed or stalled. You need it when your GSD workflows are stuck and require intervention to proceed.

Do I need specific files to run a git forensics analysis on my workflow?▼

Yes, git forensics analysis requires both git history and workflow-specific .planning artifacts to accurately diagnose issues. Without these files, the Skill cannot analyze the workflow failures or generate a diagnostic report.

Can I generate GitHub issues from workflow diagnostic reports?▼

Yes, workflow diagnostic reporting offers actionable insights to correct failed workflows and can help you create GitHub issues if necessary. This allows you to directly track and resolve the identified root causes.

What is the best way to troubleshoot a stuck GSD workflow?▼

The best way to troubleshoot a stuck GSD workflow is to run a diagnostic analysis with your problem description as the argument. This generates a structured, interactive report by analyzing your git history and .planning artifacts.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
pillippillip
11

diagnose

Diagnose bugs from logs or reproduction steps and create GitHub Issues and PRs.

Community
Advanced
dobrinz123dobrinz123

gsd-forensics

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

Community
Advanced
boettiger-labboettiger-lab
4

geo-agent-training

Analyze geo-agent logs to diagnose inefficiencies and trace root causes.

Official
Advanced