skills.rest
aslaii
aslaiiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Analyze git history and planning artifacts to diagnose GSD workflow failures.

Updated Jan 28, 2025
Search Tags:#git#reporting#diagnostics#workflows#forensics#gsd#state-analysis
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-forensics-aslaii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-forensics
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-forensics-aslaii

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 produce a structured forensic report.

Core Features & Use Cases

  • Analyze git history, .planning/ artifacts, and filesystem state to detect anomalies.
  • Generate a structured forensic report saved under .planning/forensics/ and surfaced inline for immediate review.
  • Interactive investigation and optional GitHub issue creation to capture actionable findings.

Quick Start

Execute the forensics workflow from @$HOME/.claude/get-shit-done/workflows/forensics.md to generate a structured report for the current session.

Frequently Asked Questions about gsd-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose failed git workflows and analyze repository state?▼

Diagnose failed git workflows by analyzing git history, .planning artifacts, and filesystem state. The investigation identifies anomalies in recent commits, state transitions, and artifact logs to determine what went wrong during the session.

What is a forensic report for stalled development sessions?▼

A forensic report for stalled sessions is a structured document that cites evidence from commits, files, and planning state to explain workflow failures. It is saved under .planning/forensics/ and surfaced inline for immediate review.

How do I investigate anomalies in git history and planning artifacts?▼

You investigate anomalies by running the forensics workflow to cross-reference git history with .planning artifacts and filesystem state. This interactive process detects irregular state transitions and produces a structured diagnostic report.

Can I use this forensic workflow on any project with git and planning artifacts?▼

Yes, the forensic workflow applies to failed or stalled sessions across diverse project setups. It requires git history, .planning artifacts, and filesystem state to cite evidence and generate a structured diagnostic report.

Why does my GSD workflow fail to complete and stall unexpectedly?▼

GSD workflows stall unexpectedly due to anomalies in state transitions, recent commits, or artifact logs. The forensics workflow identifies these specific failures by analyzing git history and .planning artifacts to produce a diagnostic report.

Does forensic workflow analysis support creating GitHub issues from findings?▼

Yes, forensic workflow analysis supports optional GitHub issue creation to capture actionable findings. It generates a structured forensic report saved under .planning/forensics/ and can interactively create issues from the diagnosed evidence.

Related Skills

Explore More Software Engineering Skills→
D0NMEGAD0NMEGA
8

gsd-forensics

Analyze git history and planning artifacts to identify root causes of failed GSD workflows.

Community
Advanced
thecomputer07thecomputer07

qsd-forensics

Diagnose qsd workflow failures by analyzing git history and planning artifacts.

Community
Advanced
solibluesoliblue
2

status

Summarize testing queue, last deploy, Git status, and active plans.

Community
Basic
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