code-forensics

Reconstruct software incident timelines and causal chains from logs, stack traces, commits, and test results.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill code-forensics-nlightnfotis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-forensics
Source: https://github.com/NlightNFotis/skills/tree/main/code-forensics
Command: npx skills add https://github.com/NlightNFotis/skills --skill code-forensics-nlightnfotis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you investigate software failures by reconstructing what actually happened before jumping to a fix. It is designed for situations where logs, stack traces, commits, test output, or environment changes tell an incomplete or conflicting story, and you need a defensible explanation of cause and sequence.

Core Features & Use Cases

  • Timeline reconstruction: Organizes evidence from logs, traces, CI runs, commits, and artifacts into a clear chronological sequence.
  • Earliest divergence analysis: Finds the first point where actual behavior departed from expected behavior, instead of fixating on the final visible error.
  • Causal chain building: Connects triggers, state changes, propagation, and failure symptoms into an evidence-backed narrative.
  • Use cases: Ideal for regressions after multiple changes, incidents spanning several systems, flaky or asynchronous failures, and debugging cases where previous explanations conflict.

Quick Start

Ask the AI to use the code-forensics skill to reconstruct the timeline of a regression from your logs, stack trace, recent commits, and failing test output before suggesting any fix.

Frequently Asked Questions about code-forensics

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

FAQPage Schema
How do I find the root cause of a software regression using logs and commits?

Investigate multi-system failures by cross-referencing logs and artifacts across sources to build an evidence-backed causal chain, resolving conflicting evidence and attributing triggers accurately.

What is the best way to investigate flaky or asynchronous test failures?

Trace bugs back to their true cause by applying timeline analysis to chronologically sequence logs, stack traces, and configuration changes, ensuring remediation decisions are grounded in verified facts.

How do I trace the root cause of a CI pipeline failure from conflicting logs?

Trace bugs back to their true cause by applying timeline analysis to chronologically sequence logs, stack traces, and configuration changes, ensuring remediation decisions are grounded in verified facts.

Why should I reconstruct an incident timeline before fixing a bug?

Trace bugs back to their true cause by applying timeline analysis to chronologically sequence logs, stack traces, and configuration changes, ensuring remediation decisions are grounded in verified facts.

Can I use timeline analysis for debugging incidents spanning multiple systems?

Trace bugs back to their true cause by applying timeline analysis to chronologically sequence logs, stack traces, and configuration changes, ensuring remediation decisions are grounded in verified facts.

Does incident investigation work without preserving evidence from CI runs and artifacts?

Trace bugs back to their true cause by applying timeline analysis to chronologically sequence logs, stack traces, and configuration changes, ensuring remediation decisions are grounded in verified facts.