skills.rest
TruCol270
TruCol270COMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Diagnose failed GSD workflows and generate forensic reports from git history.

1|Updated Apr 7, 2026
Search Tags:#git#workflow#planning#diagnostic#forensics#incident
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-forensics-trucol270
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-forensics
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-forensics-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong and provide a structured forensic report.

Core Features & Use Cases

  • Analyze git history and repository state to identify root causes of failures.
  • Inspect artifacts under .planning/ to track session history, ROADMAP, and PLANs.
  • Generate and save a structured forensic report to .planning/forensics/ and offer issue creation for actionable findings.

Quick Start

Run the forensics workflow to generate and save a diagnostic 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 root causes for failing git workflows in my repository?▼

To diagnose root causes for failing git workflows, you can run a forensics analysis that inspects git history, repository state, and .planning artifacts to generate a structured post-mortem report.

What is the best way to perform incident forensics on stuck GSD planning sessions?▼

Incident forensics for stuck GSD planning sessions is performed by analyzing session history, ROADMAP, and PLAN artifacts under the .planning directory to identify structural failures and generate a diagnostic report.

How do I generate a post-mortem report for failed git repository incidents?▼

You generate a post-mortem report by running a forensics workflow that verifies data sources and redacts sensitive data, saving the structured diagnostic findings to .planning/forensics/report-{timestamp}.md.

Can I automatically create GitHub issues from git history forensics findings?▼

Yes, after analyzing git history and repository state to identify root causes, the forensics workflow offers optional GitHub issue creation to track actionable findings for post-mortem remediation.

Does the forensics analysis require any external dependencies to inspect git repositories?▼

No external dependencies are required to inspect git repositories and .planning artifacts; the forensics workflow runs standalone to verify data sources, redact sensitive information, and output the forensic report.

What limitations exist when analyzing .planning artifacts for workflow diagnostic reports?▼

The workflow diagnostic analysis is limited to inspecting git history and artifacts under the .planning directory, meaning it only reports on state and data available within the local repository structure.

Related Skills

Explore More Software Engineering Skills→
Poom5741Poom5741

gsd-forensics

Diagnose failed GSD workflows by analyzing git history, artifacts, and state.

Community
Advanced
evanfang0054evanfang0054

generate-issues

Analyze Claude Code sessions and file GitHub issues for identified problems.

Community
Intermediate
tinner-deinnotinner-deinno

gsd-forensics

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

Community
Intermediate
bmad-code-orgbmad-code-org
8

bmad-os-root-cause-analysis

Correlate git history and PR metadata to generate root cause analysis reports.

Official
Advanced