Updated 2d ago
by abedegno
Exhume
Toolkit and Claude Code skills for byte-matching decompilation of old DOS games, from the Ultima Underworld II decompilation
64 GitHub stars (64)
| Period | New stars |
|---|---|
| Nov 16 | +5 |
| Nov 17 | +6 |
- 14 skills (14 skills found in its SKILL.md files)
- 12 forks (12 forks)
- 2d ago last update (Last updated 2d ago)
Install
Skills CLI
npx skills add abedegno/Exhume
Asks which skills and agents to install. Just one: npx skills add abedegno/Exhume --skill carry-forward — add -g for every project.
Claude Code
git clone https://github.com/abedegno/Exhumecp -r "Exhume/skills/carry-forward" ~/.claude/skills/
Copies the carry-forward skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add abedegno/Exhume
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
carry-forward
Use when a byte-matched decompilation is to be carried to the vendor's next (or earlier) release of the same program, or to a sibling build of the same source such as another board or product size - comparing the images with addresses allowed for, carrying the map over, rebuilding what did not change, matching what did, keeping one source for builds that differ only in constants, and proving ever…
skills/carry-forward/ on GitHub (opens in a new tab)SKILL.md -
ci-bundle
Use when a decompilation or port whose tests need private data (the original program, game data, a commercial toolchain) should run its full gate and accuracy tests on free public GitHub runners - the encrypted bundle in a private repository, the deploy key and age key, the workflow templates, the safeguards that keep the data private, and key rotation.
skills/ci-bundle/ on GitHub (opens in a new tab)SKILL.md -
fingerprint-toolchain
Use at the start of a byte-matching decompilation of a DOS executable (or, with the armcc5 profile, an Arm Cortex-M firmware image; with the ti-c2000 profile, a TI C2000 DSP image), before any matching, to identify the exact compiler, assembler, linker, memory model and switches that built it, and to prove the identification by compiling a function to the same bytes.
skills/fingerprint-toolchain/ on GitHub (opens in a new tab)SKILL.md -
firmware-verify
Use when a byte-matched Cortex-M firmware (the armcc5 profile) is to be built or changed in a way that no longer matches the original bytes - a readable rewrite, a fix, a modded build, the same C under clang - and the change must be shown to behave as the original does; with differential tests of every function, a whole-system emulator from reset, the open-toolchain build in the original's RAM la…
skills/firmware-verify/ on GitHub (opens in a new tab)SKILL.md -
link-and-diff
Use when the matched objects of a DOS decompilation are to be linked into a whole executable with the original linker in headless DOS and compared with the original, region by region; and to prove the result runs and that a source change reaches the screen. Also for an armcc5 Cortex-M firmware, whose whole image is rebuilt in pieces under MDK-Lite's 32 KB limit and compared byte for byte, and for…
skills/link-and-diff/ on GitHub (opens in a new tab)SKILL.md -
map-binary
Use after the toolchain is fingerprinted, to lay out a DOS executable for matching - find every code segment and procedure, split it into original source files, recover original function names from a symbol-bearing sibling build (another platform's release), and write the target tables agents match against.
skills/map-binary/ on GitHub (opens in a new tab)SKILL.md -
match-asm
Use when rebuilding a hand-written assembly module of an old DOS program as assembler source that assembles byte for byte to the original (TASM 2.0 for the Borland profile), starting from tools/asmgen.py's generated draft and turning it into source a period programmer would have written.
skills/match-asm/ on GitHub (opens in a new tab)SKILL.md -
match-file
Use when decompiling one C source file of an old DOS program (or of an armcc5 or TI C2000 firmware image) into C that recompiles byte for byte to the original - the per-file loop of writing C, compiling in headless DOS, reading instruction diffs and restructuring until every function matches and verify passes. Also the brief to give an agent that matches a file.
skills/match-file/ on GitHub (opens in a new tab)SKILL.md -
modding-build
Use when the sources of a byte-matched, exactly linked DOS decompilation are to be changed by any size (a fix, a mod, the first step of a port) and still linked into a running executable; and to audit the layout for addresses written as numbers, which matching and the exact link cannot see. Also for an armcc5 Cortex-M firmware: new code in free flash, and proof that the original's bytes changed o…
skills/modding-build/ on GitHub (opens in a new tab)SKILL.md -
orchestrate
Use when running a whole byte-matching decompilation with several AI agents - choosing models, how many agents at once, per-file build budgets, Codex drafts with Claude finishers, the build queue for sandboxed agents, and keeping agents from clobbering each other; with the costs measured on UW2. Also for an armcc5 firmware - a git worktree and a cloned Wine prefix per agent, the full gate before…
skills/orchestrate/ on GitHub (opens in a new tab)SKILL.md -
port-and-verify
Use when a byte-matched, exactly linked DOS decompilation with a working modding build is to become a native program for macOS, Linux or Windows that behaves exactly as the original - the portability layer, link stubs, the platform layer, assembly through a static recompiler and then readable C, and verification against DOS by record and replay, golden references and routine fuzzing; with the sou…
skills/port-and-verify/ on GitHub (opens in a new tab)SKILL.md -
port-prep
Use when a byte-matching decompilation is complete or nearly so and someone wants to port, modernise or modify the program - lists what the matched tree still lacks, what to keep as the reference, and the checks that keep a port honest against the original.
skills/port-prep/ on GitHub (opens in a new tab)SKILL.md -
readability-pass
Use when a byte-matched, exactly linked DOS decompilation (or an armcc5 Cortex-M or TI C2000 firmware tree) is to be made readable without changing a byte - a build gate, shared headers, named constants, struct fields and accessors, original file names and subsystem directories, comments and findings - each step proved by the gate; and when running agents to do it.
skills/readability-pass/ on GitHub (opens in a new tab)SKILL.md -
verify-and-merge
Use when a source file reports WHOLE SEGMENT MATCHES and is to be accepted into a byte-matching decompilation - check everything match.py masks (fixups, data, BSS, far data, names) and merge the file through the gates that keep symbols.tsv and matched.txt consistent. Also use after any rename.
skills/verify-and-merge/ on GitHub (opens in a new tab)SKILL.md
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.