crash-investigator

Capture Mesen2 emulator crash traces and resolve symbols into Markdown reports.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/scawful/afs_scawful --skill crash-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crash-investigator
Source: https://github.com/scawful/afs_scawful/tree/main/skills/crash-investigator
Command: npx skills add https://github.com/scawful/afs_scawful --skill crash-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous crash analysis for Mesen2 captures execution traces upon crash or pause, resolves symbols, and generates annotated reports for debugging.

Core Features & Use Cases

  • Automatic crash detection: Watches Mesen2 for pauses or breakpoints and triggers dumps.
  • Trace capture & symbol resolution: Retrieves CPU state and resolves addresses to symbols and source lines.
  • Report generation: Produces Markdown-based crash reports ready for review or LLM analysis.

Quick Start

Start crash-investigator, run Mesen2, trigger a crash, and review the generated crash_reports in the repository.

Frequently Asked Questions about crash-investigator

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

FAQPage Schema
How do I automate emulator crash analysis and generate a debugging report?

Automated crash analysis captures execution traces during emulator crashes, resolves symbols to source lines, and generates annotated Markdown reports for debugging.

What do I need to resolve symbols during a Mesen2 crash dump?

Resolving symbols during a Mesen2 crash dump requires z3ed with symbol support, a tracing tool, and a ROM with symbol files to map addresses.

How does automatic crash detection work for emulator gaming sessions?

Automatic crash detection monitors the emulator for pauses or breakpoints during gaming sessions and triggers trace dumps when crashes occur.

What is the output format for emulator crash reports?

The output format for emulator crash reports is Markdown, providing annotated traces and CPU state details ready for direct review or LLM analysis.

Can I use this crash analysis tool without a ROM with symbol files?

No, this crash analysis tool requires a ROM with symbol files to map memory addresses to symbols and source lines.