skills.rest
scawful
scawfulCOMMUNITY
Explore all skills by this author →
Website𝕏@scawfulGitHub

mesen2-oos-debugging

Reproduce and triage Mesen2-OOS bugs via the socket CLI.

Updated Dec 30, 2025
Search Tags:#debugging#labels#mesen2#oos#socket-cli#rom#memory-inspection
One-click install
npx skills add https://github.com/scawful/afs_scawful --skill mesen2-oos-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mesen2-oos-debugging
Source: https://github.com/scawful/afs_scawful/tree/main/skills/mesen2-oos-debugging
Command: npx skills add https://github.com/scawful/afs_scawful --skill mesen2-oos-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables end-to-end debugging of Mesen2-OOS sessions by controlling the socket CLI to reproduce bugs, capture evidence, and map runtime behavior back to labels and source.

Core Features & Use Cases

  • Drive Mesen2-OOS from the socket CLI to reproduce bugs, capture evidence, and map runtime behavior back to labels and source.
  • Support a structured debugging flow: stabilize, label, reproduce, inspect, annotate, and verify.
  • Integrates with symbol/label tooling and isolated-instance workflows to prevent profile conflicts in collaborative environments.

Quick Start

Launch Mesen2-OOS with the target ROM from the repo root and connect using the socket CLI to begin debugging.

Frequently Asked Questions about mesen2-oos-debugging

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

FAQPage Schema
How do I debug a Mesen2 out-of-sync issue using the socket CLI?▼

To debug a Mesen2 out-of-sync issue, use the socket CLI to reproduce bugs, capture breakpoint evidence, and map runtime memory behavior back to source labels. This skill drives the structured stabilization and reproduction workflow.

What's the best way to capture and triage Mesen2 ROM crashes across different labels?▼

The best way to triage Mesen2 ROM crashes is applying the structured debugging flow: stabilize, label, reproduce, inspect, annotate, and verify using the socket CLI to capture evidence across ROMs and labels.

How does memory inspection work when debugging Mesen2 sessions?▼

Memory inspection works by connecting the socket CLI to a running Mesen2 instance, allowing you to evaluate runtime memory against breakpoints and map the inspected values directly back to your source labels.

Do I need a running Mesen2 instance and target ROM to use the socket CLI for debugging?▼

Yes, you need a running Mesen2 instance and a target ROM. Proper environment setup with the described CLI tools and scripts is required to execute the socket-based debugging and repro workflow.

Can I use isolated Mesen2 instances to prevent profile conflicts in collaborative debugging?▼

Yes, the debugging workflow integrates with isolated-instance workflows and symbol/label tooling to prevent profile conflicts, ensuring stable collaborative environments when reproducing bugs via the socket CLI.

Related Skills

Explore More Software Engineering Skills→
scawfulscawful

mesen2-oos-cli

Redirect legacy mesen2-oos-cli prompts to the mesen2-oos-debugging workflow.

Community
Basic
vzcovzco
15

trace-writes

Trace memory writes in x64 processes using hardware breakpoints and disassembly.

Official
Intermediate
scawfulscawful

memory-cartographer

Identify SNES WRAM addresses that change during gameplay via Mesen2 socket server.

Community
Advanced
granietgraniet
247

pokemon-player

Automate classic Pokemon gameplay via headless emulation with RAM state reading and vision analysis.

Community
Advanced