gearboy-debugging

Debug Game Boy games via Gearboy MCP server with execution control.

1.2k|159|Updated Jul 19, 2012
One-click install
npx skills add https://github.com/drhelius/Gearboy --skill gearboy-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gearboy-debugging
Source: https://github.com/drhelius/Gearboy/tree/main/skills/gearboy-debugging
Command: npx skills add https://github.com/drhelius/Gearboy --skill gearboy-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, unzip, and includes scripts (resource) components.

What problem does it solve?

This Skill helps developers debug and trace Game Boy family games by leveraging the Gearboy MCP server. It provides structured workflows to control execution, inspect the SM83 CPU and hardware, manage breakpoints, read memory, disassemble code, trace instructions, and analyze rendering/timing issues, enabling efficient diagnosis and reverse engineering.

Core Features & Use Cases

  • Control execution: pause, step, and breakpoints across GB/GBC/SGB using the MCP server.
  • Inspect hardware state: read CPU registers, LCD, APU, SGB, and memory areas.
  • Disassembly & tracing: disassemble code, view call stacks, set breakpoints, and capture trace logs.
  • Time travel debugging: rewind snapshots to compare states and verify fixes.
  • Use cases: debugging homebrew, reverse engineering game logic, diagnosing graphics or audio issues.

Quick Start

Launch Gearboy as an MCP server, connect your AI client, load a ROM, then pause or step to begin debugging.

Frequently Asked Questions about gearboy-debugging

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

FAQPage Schema
How do I debug Game Boy games using an MCP server?

The Skill helps debug and trace Game Boy family titles by leveraging the Gearboy MCP server to control execution, inspect hardware state, manage breakpoints, and capture trace logs for efficient diagnosis.

How do I inspect SM83 CPU registers and memory during a Game Boy debugging session?

During a Game Boy debugging session, you can inspect SM83 CPU registers, LCD, APU, SGB, and specific memory areas by pausing execution through the MCP server and querying the current hardware state.

Can I disassemble code and trace instructions for Game Boy homebrew development?

Yes, you can disassemble code, view call stacks, set breakpoints, and capture trace logs for Game Boy homebrew development by utilizing the execution control features provided through the Gearboy MCP server integration.

Does Game Boy time travel debugging let me rewind snapshots to compare states?

Time travel debugging allows you to rewind snapshots to compare hardware and memory states, enabling you to verify fixes and analyze execution flow when reverse engineering GB, GBC, or SGB titles.

What do I need to start tracing Game Boy ROM execution?

To start tracing Game Boy ROM execution, you need the Gearboy MCP server running, an active MCP client integration, and command-line tools curl and unzip installed to load ROMs and control stepping.

How do I diagnose graphics and audio timing issues in Game Boy emulators?

You diagnose graphics and audio timing issues by using the Gearboy MCP server to inspect LCD and APU hardware state, set breakpoints at relevant routines, and capture instruction trace logs during execution.