Agent skill

Nes Rom Debug

by jonathanpeppers in jonathanpeppers/dotnes

Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler.

MITAuto-check passedDevelopment

Install Nes Rom Debug

skills CLI
$ npx skills add jonathanpeppers/dotnes --skill nes-rom-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jonathanpeppers/dotnes nes-rom-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jonathanpeppers/dotnes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/nes-rom-debug .claude/skills/nes-rom-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nes-rom-debug
GitHub stars
780
Token cost
~1.5k tokens
SKILL.md length
509 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler.

  • Works in 5 steps: File sizes → Total byte differences (header / PRG /… → Contiguous diff groups with NES addresses → …
  • The user wants to disassemble a .nes ROM
  • SKILL.md covers Available Scripts, NES ROM Format (iNES), Common Debugging Workflows and 6502 Quick Reference
  • Calls python and dotnet

What it does

Nes Rom Debug is an agent skill from jonathanpeppers/dotnes. Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler. Use this skill whenever the user wants to disassemble a .nes ROM, inspect 6502 machine code, compare two NES ROMs side-by-side, debug transpiler output, investigate byte differences between a cc65 reference ROM and a dotnes ROM, or understand what 6502 instructions the transpiler emitted. Also use when the user mentions disasm, disassembly, PRG ROM, ROM bytes, NES addresses, or wants to look at the hex/binary output of a build. Even if…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. It works with .NET. The repository describes itself as: .NET for the NES game console. The licence is MIT.

When your agent uses it

  • The user wants to disassemble a .nes ROM
  • Inspect 6502 machine code
  • Compare two NES ROMs side-by-side
  • Debug transpiler output

Example prompts

  • “the ROM looks wrong”
  • “what did the transpiler emit”
  • “/nes-rom-debug”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. File sizes
  2. Total byte differences (header / PRG / CHR breakdown)
  3. Contiguous diff groups with NES addresses
  4. Side-by-side disassembly of the largest diff region with match/mismatch markers
  5. Instruction mismatch count (ignoring absolute addresses, since the two compilers may place subroutines at different offsets)

What it can do on your machine

Read from SKILL.md and the folder at commit 42ca23d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python
    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nes Rom Debug loads about 1.5k tokens when it runs. Until then it costs about 161 tokens; SKILL.md has 509 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~161
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jonathanpeppers/dotnes at commit 42ca23d, republished under its MIT licence (© jonathanpeppers). 509 words, ~1,480 tokens.

Download SKILL.mdSave it as .claude/skills/nes-rom-debug/SKILL.md (or your agent's skills folder).
name
nes-rom-debug
description
Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler. Use this skill whenever the user wants to disassemble a .nes ROM, inspect 6502 machine code, compare two NES ROMs side-by-side, debug transpiler output, investigate byte differences between a cc65 reference ROM and a dotnes ROM, or understand what 6502 instructions the transpiler emitted. Also use when the user mentions disasm, disassembly, PRG ROM, ROM bytes, NES addresses, or wants to look at the hex/binary output of a build. Even if the user just says something like "the ROM looks wrong" or "what did the transpiler emit", this skill applies.

NES ROM Debug

Tools and knowledge for disassembling NES ROMs and debugging dotnes transpiler output.

Available Scripts

disasm.py — 6502 Disassembler

Disassembles the PRG ROM section of an iNES (.nes) file into human-readable 6502 assembly.

bash
python scripts/disasm.py <file.nes> [start_hex] [end_hex]
  • file.nes — Path to the NES ROM file
  • start_hex — (Optional) Start NES address in hex, default 8000
  • end_hex — (Optional) End NES address in hex, default end of PRG

Examples:

Note: .nes files are build outputs — run dotnet build in the sample directory first.

bash
# Disassemble the entire PRG ROM
python scripts/disasm.py samples/hello/hello.nes

# Disassemble only the main() region
python scripts/disasm.py samples/hello/hello.nes 8500 8600

# Disassemble the interrupt vectors area
python scripts/disasm.py samples/hello/hello.nes FF00 FFFF

Output format:

$8500: A9 02     LDA #$02
$8502: 20 61 85  JSR $8561
$8505: 85 17     STA $17
$8507: D0 F7     BNE $8500

Each line shows: $ADDR: HEX_BYTES MNEMONIC OPERAND

compare_rom.py — Side-by-Side ROM Comparison

Compares two NES ROMs with byte-level and instruction-level analysis. Use this to verify dotnes output against a cc65 reference ROM.

bash
python scripts/compare_rom.py <reference.nes> <dotnes.nes>

Output includes:

  1. File sizes
  2. Total byte differences (header / PRG / CHR breakdown)
  3. Contiguous diff groups with NES addresses
  4. Side-by-side disassembly of the largest diff region with match/mismatch markers
  5. Instruction mismatch count (ignoring absolute addresses, since the two compilers may place subroutines at different offsets)
ildump.cs — IL Opcode Dumper

Dumps the .NET IL opcodes from a compiled DLL — useful for understanding what IL the transpiler will process.

bash
dotnet run scripts/ildump.cs -- <path-to-dll>

NES ROM Format (iNES)

Understanding the binary layout helps interpret disassembly output:

Offset    Size     Content
0x00      16       iNES header (starts with "NES\x1A")
0x10      32768    PRG ROM (mapped to NES $8000-$FFFF)
0x8010    8192     CHR ROM (pattern tables for tiles/sprites)

Key NES addresses:

  • $8000-$85AD — neslib runtime and built-in subroutines (palette, PPU, NMI handler, stack ops)
  • $85AE+ — main() and user code (exact layout varies per sample)
  • $FFFA — NMI vector (2 bytes, little-endian)
  • $FFFC — RESET vector (2 bytes, little-endian — entry point)
  • $FFFE — IRQ vector (2 bytes, little-endian)

File offset → NES address: nes_addr = 0x8000 + (file_offset - 16) NES address → file offset: file_offset = (nes_addr - 0x8000) + 16

Common Debugging Workflows

"The ROM doesn't match the reference"
  1. Run compare_rom.py to identify where bytes differ
  2. Use disasm.py on both ROMs targeting the diff region to see the instructions
  3. Check if differences are just address relocations (compare_rom normalizes these) or actual logic differences
bash
python scripts/compare_rom.py reference.nes output.nes
# If diff at $8600-$8620:
python scripts/disasm.py reference.nes 85F0 8630
python scripts/disasm.py output.nes 85F0 8630
Show full SKILL.md (211 more words)Show less
"What did the transpiler emit for my code?"
  1. Build the sample: cd samples/hello && dotnet build
  2. Dump the IL to see what C# compiled to: dotnet run scripts/ildump.cs -- samples/hello/bin/Debug/net10.0/hello.dll
  3. Disassemble the ROM to see the 6502 output: python scripts/disasm.py samples/hello/bin/Debug/net10.0/hello.nes 8500
"Where is main() in the ROM?"

The RESET vector at $FFFC points to the startup code, which eventually jumps to main. To find it:

bash
# Look at the last few bytes for the vectors
python scripts/disasm.py myrom.nes FFF0 FFFF

# The RESET vector value tells you where startup is
# Then disassemble from there to find the JMP to main
"Comparing test output against verified snapshot"

When TranspilerTests.Write fails, the test produces a .received.bin alongside the .verified.bin. Compare them:

bash
# The test DLLs are in src/dotnes.tests/Data/
# Build the test project to get the .received.bin
python scripts/compare_rom.py path/to/verified.bin path/to/received.bin

6502 Quick Reference

The most common instructions you'll see in dotnes output:

OpcodeMnemonicMeaning
A9LDA #immLoad accumulator with immediate value
A5LDA zpgLoad accumulator from zero page
ADLDA absLoad accumulator from absolute address
85STA zpgStore accumulator to zero page
8DSTA absStore accumulator to absolute address
20JSR absJump to subroutine
60RTSReturn from subroutine
4CJMP absJump to address
D0BNE relBranch if not equal (Z=0)
F0BEQ relBranch if equal (Z=1)
C9CMP #immCompare accumulator with immediate
E6INC zpgIncrement zero page location
C6DEC zpgDecrement zero page location

Zero page addresses used by dotnes:

  • $17 — TEMP
  • $22-$23 — sp (cc65 software stack pointer)
  • $0325+ — Local variables

© jonathanpeppers, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/nes-rom-debug of jonathanpeppers/dotnes.

Open the folder on GitHubat commit 42ca23d

Compare with similar skills

Nes Rom Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nes Rom Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nes Rom Debug this skilljonathanpeppers/dotnes780—~1.5kAutomated safety check: PassMIT
Dotnet Debuggingnovotnyllc/dotnet-artisan233—~2.1kAutomated safety check: PassMIT
Okojo Node Ink Debugakeit0/okojo160—~798Automated safety check: PassMIT
MSBuildLocator .NET Core Loadermicrosoft/MSBuildLocator263—~1.1kAutomated safety check: PassCustom licence
Raven Debug Compilermarinasundstrom/raven108—~1.6kAutomated safety check: PassMIT
Development Workflowrunceel/ReactiveProperty944—~1.4kAutomated safety check: PassMIT

Similar skills

  • Dotnet Debugging

    novotnyllc/dotnet-artisan

    Debugs Windows and Linux/macOS applications (native, .NET/CLR, mixed-mode) with WinDbg MCP (crash dumps, !analyze, !syncblk, !dlk, !runaway, !dumpheap, !gcroot, BSOD), dotnet-dump, lldb with SOS…

    233 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Debug Okojo.Node large-app failures through sandbox/OkojoInkProbe and sandbox/OkojoNodeDebugSandbox.

    160 GitHub stars~798 tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • MSBuildLocator .NET Core Loader

    microsoft/MSBuildLocator

    Official

    Reference for how MSBuildLocator loads MSBuild assemblies and finds the .NET SDK on .NET Core hosts, for anyone editing or debugging that loader code.

    263 GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Raven Debug Compiler

    marinasundstrom/raven

    Debug workflow for Raven compiler analysis and emission issues using rvn frontend tooling and the rvnc compiler driver.

    108 GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Development Workflow

    runceel/ReactiveProperty

    ReactiveProperty repository development policy. An agent skill from runceel/ReactiveProperty.

    944 GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • MSBuildLocator .NET Framework Loader

    microsoft/MSBuildLocator

    Official

    Explains how MSBuildLocator loads MSBuild assemblies and finds Visual Studio installs on the .NET Framework net46 target, for anyone editing or reviewing that code.

    263 GitHub stars~745 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jonathanpeppers/dotnes

  • Code Review

    jonathanpeppers/dotnes

    Review dotnes pull requests against established repository rules.

    780 GitHub stars~2.1k tokensUpdated 14 days ago
    Auto-check passed
  • Nes Decompile

    jonathanpeppers/dotnes

    Decompile NES ROM files (.nes) into C projects that can be rebuilt with dotnes.

    780 GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed
  • PR Iterate

    jonathanpeppers/dotnes

    Iterate on a GitHub pull request from a coding agent (like Copilot coding agent) until it's ready for human review.

    780 GitHub stars~2.4k tokensUpdated 14 days ago
    Auto-check passed

Works with

Categories

Questions about Nes Rom Debug

What does Nes Rom Debug do?

Disassemble and debug NES ROM files (.nes) produced by the dotnes transpiler. Nes Rom Debug is an agent skill from jonathanpeppers/dotnes.nes) produced by the dotnes transpiler.

When should I use Nes Rom Debug?

Nes Rom Debug fits situations like: the user wants to disassemble a .nes ROM; inspect 6502 machine code; compare two NES ROMs side-by-side; debug transpiler output.

How do I install Nes Rom Debug in Claude Code?

Run `npx skills add jonathanpeppers/dotnes --skill nes-rom-debug -a claude-code`. Or copy the skill folder (.github/skills/nes-rom-debug in jonathanpeppers/dotnes) into .claude/skills/nes-rom-debug in your project. Claude Code loads it when a task matches its description.

How do I install Nes Rom Debug in Codex?

Run `npx skills add jonathanpeppers/dotnes --skill nes-rom-debug -a codex`. Or copy the skill folder (.github/skills/nes-rom-debug in jonathanpeppers/dotnes) into .agents/skills/nes-rom-debug in your project. Codex loads it when a task matches its description.

Can I use Nes Rom Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jonathanpeppers/dotnes --skill nes-rom-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nes-rom-debug, .gemini/skills/nes-rom-debug, .github/skills/nes-rom-debug and .opencode/skills/nes-rom-debug in your project.

What does Nes Rom Debug need to run?

Going by SKILL.md and its folder, Nes Rom Debug needs the command-line tools its instructions call (python and dotnet). Our summary lists: Python 3.

Does Nes Rom Debug access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nes Rom Debug safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nes Rom Debug use?

Nes Rom Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nes Rom Debug use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nes Rom Debug?

Skills that share tags, products or a category with Nes Rom Debug: Dotnet Debugging (novotnyllc/dotnet-artisan, 233 stars), Okojo Node Ink Debug (akeit0/okojo, 160 stars), MSBuildLocator .NET Core Loader (microsoft/MSBuildLocator, 263 stars) and Raven Debug Compiler (marinasundstrom/raven, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nes Rom Debug?

jonathanpeppers (a GitHub user) maintains it in jonathanpeppers/dotnes, which has 780 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 23, 2026.

Source: jonathanpeppers/dotnes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.