match-data-file

Update YAML data entries and C source mappings during ROM decompilation.

178|10|Updated Sep 28, 2024
One-click install
npx skills add https://github.com/cdlewis/snowboardkids2-decomp --skill match-data-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: match-data-file
Source: https://github.com/cdlewis/snowboardkids2-decomp/tree/main/.claude/skills/match-data-file
Command: npx skills add https://github.com/cdlewis/snowboardkids2-decomp --skill match-data-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align binary data segments with corresponding C source definitions by updating project data to reflect matches during ROM decompilation.

Core Features & Use Cases

  • Update YAML segment entries to mark when a data segment is defined in the C file, aligning code and data mappings.
  • Adjust mappings from data segments to the assembler object by changing the data tag to .data in the relevant entries.
  • Enable iterative build verification to surface missing data and guide fixes during decompilation.

Quick Start

Edit the YAML entry for the new data segment and run the build-verify workflow to confirm the match.

Frequently Asked Questions about match-data-file

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

FAQPage Schema
How do I align binary data segments with C source definitions during ROM decompilation?

Align binary data segments with C source definitions by editing YAML segment entries to mark data definitions and updating data tags to .data. Run the build verification script iteratively to detect mismatches and guide fixes.

Why does my build verification fail after mapping data segments to C sources?

Build verification fails during data segment matching when YAML entries lack proper .data tags or C source definitions are missing. Edit the YAML configuration and C files to align mappings, then rerun verification to confirm fixes.

What's the best way to update YAML data segment entries for ROM decompilation projects?

Update YAML data segment entries by changing the data tag to .data in relevant assembler object mappings and marking when segments are defined in the C file. This aligns code and data mappings across the decompilation project.

When do I need to adjust data tags to .data in assembly decompilation workflows?

Adjust data tags to .data when binary data segments are defined in C source files during ROM decompilation. This updates mappings from data segments to the assembler object and ensures build verification detects remaining mismatches.

Can I use build verification to detect missing data segment matches in C sources?

Build verification detects missing data segment matches by surfacing mismatches between YAML entries and C source definitions. Run the script iteratively after editing YAML and C files to confirm all data segments are properly aligned.