coding-session-forensics

Name: coding-session-forensics
Availability: InStock
Author: Dektora

Analyze failed DekSpec construction sessions using git/worktree evidence and generate forensic reports.

Updated Jun 2, 2026

Search Tags:#diagnosis #session analysis #forensics #dekspec #construction session

Ready to run

npx skills add https://github.com/Dektora/dekspec-public --skill coding-session-forensics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-session-forensics
Source: https://github.com/Dektora/dekspec-public/tree/main/plugins/dekspec/skills/coding-session-forensics
Command: npx skills add https://github.com/Dektora/dekspec-public --skill coding-session-forensics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose stuck or failed DekSpec construction sessions by collecting evidence, detecting failure fingerprints, and generating a forensic report with a root-cause hypothesis and recovery commands.

Core Features & Use Cases

Post-Mortem Analysis: Investigates stuck, failed, or anomalous DekSpec construction sessions.
Evidence Collection: Gathers git/worktree/bead/linkage evidence.
Anomaly Detection: Identifies failure fingerprints like stuck loops, orphaned worktrees, and mid-red crashes.
Structured Report: Writes a forensic report with a root-cause hypothesis and recommended recovery commands.
Use Case: If a coding session hangs or ends in an unusual state, use this Skill to get a systematic diagnosis and recovery recommendations.

Quick Start

Perform a post-mortem on the 'INT-204' coding session using the coding-session-forensics skill.

Frequently Asked Questions about coding-session-forensics

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

FAQPage Schema

How do I diagnose a stuck DekSpec construction session?▼

To diagnose a stuck DekSpec construction session, analyze git repository and worktree evidence to detect failure fingerprints like orphaned worktrees or mid-red crashes, generating a structured forensic report with root-cause hypotheses and recovery commands.

What causes DekSpec construction sessions to fail or hang?▼

DekSpec construction sessions fail or hang due to common anomalies like stuck loops, orphaned worktrees, and mid-red crashes. Analyzing git, worktree, and linkage evidence identifies these specific failure fingerprints to determine the root cause.

How do I perform a post-mortem analysis on a failed coding session?▼

Perform a post-mortem analysis on a failed coding session by collecting git, worktree, bead, and linkage evidence. This process detects anomalies and outputs a structured forensic report with a root-cause hypothesis and recommended recovery commands.

Do I need git repository access to analyze a DekSpec session?▼

Yes, you need access to the session's git repository and DekSpec audit tools to analyze a DekSpec session. Evidence collection relies on examining git history, worktrees, and linkage data to accurately detect failure modes.

What is the best way to recover from an orphaned worktree in DekSpec?▼

The best way to recover from an orphaned worktree in DekSpec is to run a forensic analysis to detect the anomaly, then execute the specific recovery commands provided in the generated structured report to restore the session state.