メニュー
Match a data segment by mapping it to an existing C file and replacing extern declarations with ordered definitions. Use when asked to match, add, split, or fix a .data segment in snowboardkids.yaml.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/cdlewis/snowboardkids-decomp --skill match-data-segmentコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Match a segment's bss data by replacing extern declarations with the appropriate definitions. Use when asked to match, add, split, or fix a .bss segment, especially after checksum failures from bss symbol layout, shifted VRAM labels, queue/stack buffers, or unresolved bss externs.
Decomp-Permuter is a tool that automatically permutes C files to better match a target binary. Use this skill when you are decompiling a function and it is almost matching except for some register differences (i.e. 95%+).
Use this skill if you need to decompile a function that uses F3DEX. The presence of the Gfx type or gRegionAllocPtr are strongly indicative of an F3DEX or S2DEX microcode function.
| name | match-data-segment |
| description | Match a data segment by mapping it to an existing C file and replacing extern declarations with ordered definitions. Use when asked to match, add, split, or fix a .data segment in snowboardkids.yaml. |
Code, data, rodata and bss are all defined as separate segments in snowboardkids.yaml. The first step of matching a new data segment is to update the appropriate data segment entry to mark is as defined in the existing C file (code segment).
For example if you are asked to match the data segment for code segment 0x8A40:
- [0x88D30, data, 8A40]
Should be changed to:
- [0x88D30, .data, 8A40]
Rebuild the project by running:
./tools/build-and-verify.sh
The build will now fail because we have not yet added the expected data. But these error messages can be instructive for telling us what data is needed, etc.
Examine the assembly code for the data segment, this is located in asm/data/. So our above example would be located in asm/data/8A40.data.s. Remember that the N64 rom is big endian.
Take the labeled data from the data file and add the appropriate variable definitions to the C file (`src/8A40.c in our example).
Note that the C file will have missing data definitions already but they will be externs. You should add the variable definitions in the order in which they appear in the data file (do not follow the ordering of the externs).
Rebuild the project by running:
./tools/build-and-verify.sh
You will likely encounter build errors or checksum failures. Work through the errors and resolve any checksum mismatches.