skills.rest
thecomputer07
thecomputer07COMMUNITY
Explore all skills by this author →
GitHub

qsd-forensics

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

Updated Apr 13, 2026
Search Tags:#workflow#reports#diagnostics#forensics#git-history#state-analysis#qsd
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-forensics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qsd-forensics
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-forensics
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-forensics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and diagnose failures in qsd workflow executions by analyzing git history, planning artifacts, and repository state to identify root causes and provide actionable remediation guidance.

Core Features & Use Cases

  • Forensic analysis of git history, session state, and planning artifacts to surface anomalies and gaps.
  • Structured forensic report generation saved to .planning/forensics/report-{timestamp}.md with inline findings and recommendations.
  • Interactive investigation workflow with optional GitHub issue creation for actionable findings and remediation tasks.

Quick Start

Run the forensic workflow against your qsd project to generate a comprehensive diagnostic report.

Frequently Asked Questions about qsd-forensics

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

FAQPage Schema
How do I diagnose a crashed or aborted qsd workflow session?▼

Run a forensic analysis on git history, session state, and planning artifacts to detect failures in qsd workflows. This read-only investigation surfaces anomalies and generates a structured diagnostic report with actionable remediation steps.

What is the best way to investigate root causes of failed workflow executions in git history?▼

Conduct a read-only forensic analysis of git history and planning artifacts to identify workflow execution failures. This process outlines root causes using evidence-backed findings and generates structured reports for actionable remediation.

Can I generate structured diagnostic reports for stuck qsd project sessions?▼

Yes, structured forensic reports are generated under .planning/forensics/report-{timestamp}.md. These reports contain inline findings and recommendations derived from analyzing git history and repository state for stuck qsd sessions.

Does forensic state analysis support creating GitHub issues for remediation tasks?▼

Yes, the interactive investigation workflow supports optional GitHub issue creation. This allows you to track actionable findings and remediation tasks directly from the generated forensic diagnostic report.

Do I need any dependencies to run read-only forensic analysis on planning artifacts?▼

No external dependencies are required. The forensic workflow performs read-only analysis on planning artifacts, git history, and repository state independently to surface anomalies and generate diagnostic reports.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
TruCol270TruCol270
1

gsd-forensics

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

Community
Advanced
jedmamostojedmamosto

gsd-forensics

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

Community
Advanced
himanshu231204himanshu231204
2

terminal-ops

Log terminal commands, git state changes, and test results for verifiable repository operations.

Community
Advanced