split-maintenance
Maintain config/GCBE7D/splits.txt and its generated companions. Use when Codex needs to add or replace unit ranges, import split data from the backup file, seed split ownership, or reason about normalized unit names like ai_1.c and GBA_1.c.
Best use case
split-maintenance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Maintain config/GCBE7D/splits.txt and its generated companions. Use when Codex needs to add or replace unit ranges, import split data from the backup file, seed split ownership, or reason about normalized unit names like ai_1.c and GBA_1.c.
Teams using split-maintenance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/split-maintenance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How split-maintenance Compares
| Feature / Agent | split-maintenance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Maintain config/GCBE7D/splits.txt and its generated companions. Use when Codex needs to add or replace unit ranges, import split data from the backup file, seed split ownership, or reason about normalized unit names like ai_1.c and GBA_1.c.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Split Maintenance ## Core Rules - Edit `config/GCBE7D/splits.txt`, not `config/GCBE7D/splits.generated.txt`. - Rerun `python configure.py --version GCBE7D --toolchain prodg35` after changing splits or config files. - Treat `config/GCBE7D/splits.elf_import_backup.txt` as a source of candidate ranges, not as something to copy wholesale without review. ## Preferred Tools For safe import from the backup file: - `python tools/add_split_from_backup.py --unit <unit>` - Start with the default `.text,.rodata` import unless the task clearly needs more sections. For seed generation from map-style comments: - `python tools/generate_seed_splits.py --version GCBE7D` For lookup while editing: - `python tools/ai_lookup_unit.py <unit-or-address>` - `python tools/ai_context.py <unit-or-address>` ## Working Pattern 1. Resolve the target unit and inspect its current ranges. 2. Import or edit only the sections you actually need. 3. Rerun configure. 4. Build the affected object or run a full `ninja` if the change is broad. ## References - Read [references/splits-format.md](references/splits-format.md) for the file format, generated outputs, and normalization rules.
Related Skills
task-pack
Generate and run provider-neutral decompilation task packs in crashwoc-decomp. Use when an agent should turn a unit, function, or decomp.me bundle into a self-contained task pack and run it against any backend (print, copilot, codex, claude, aider, or gemini).
symbol-lookup
Lookup symbols, addresses, units, and match metadata in crashwoc-decomp. Use when Codex needs to map a function or global to config/GCBE7D/symbols.txt, split ownership, build/GCBE7D/report.json, or fallback DWARF lines.
project-onboarding
Onboard Codex to crashwoc-decomp. Use when working in this repository and Codex needs the project layout, build and verification commands, generated-file rules, helper tooling, or the standard workflow for Crash Bandicoot: The Wrath of Cortex GameCube decompilation.
match-workflow
Drive symbol-to-verification matching work in crashwoc-decomp. Use when Codex needs to take a symbol or unit from lookup through context gathering, narrow local builds, and final regression checks.
ghidra-workflow
Query the local Crash WOC Ghidra project through analyzeHeadless.bat for function lookup, decompilation, disassembly, and datatype inspection.
build-triage
Diagnose build failures, progress regressions, and single-object compile problems in crashwoc-decomp. Use when Codex needs to narrow a failing target, inspect report data, or summarize changes from ninja changes.
agent-orchestration
Orchestrate one Crash WOC unit or one function with Copilot using the repo-local helper scripts, prompt entry points, and a one-writer-at-a-time workflow.
decomp-match
Autonomous matching-decompilation workflow for Crash WOC GameCube units. Use when the agent needs to decomp-match functions in a C source file.
splitmixternary-opine
Political Repetition as Hyperrealpolitik - deterministic opinion formation via SplitMixTernary across all encountered languages. The eternal return of the trit.
mlx-jax-splitmix
MLX on Apple Silicon with JAX-style SplitMix64 PRNG. Deterministic color generation with GPU acceleration.
splitwise-automation
Automate Splitwise tasks via Rube MCP (Composio). Always search tools first for current schemas.
thor-maintenance
Maintain THOR installs using thor-util: update signatures, upgrade versions, download offline packs, generate reports, manage YARA-Forge. Use when the user asks about updating/upgrading/report generation.