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.

8 stars

Best use case

match-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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.

Teams using match-workflow 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

$curl -o ~/.claude/skills/match-workflow/SKILL.md --create-dirs "https://raw.githubusercontent.com/denzi-gh/crashwoc-decomp/main/tools/skills/match-workflow/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/match-workflow/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How match-workflow Compares

Feature / Agentmatch-workflowStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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.

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.

Related Guides

SKILL.md Source

# Match Workflow

## Standard Loop

1. Resolve the target with `python tools/ai_lookup_symbol.py ...`, `python tools/ai_lookup_unit.py ...`, or `python tools/ai_context.py ...`.
2. If the task starts from a file or unit, run `python tools/ai_match_plan.py <unit-or-path>` to list the remaining functions and pick the next target.
3. Build the context target with `ninja build/GCBE7D/src/<unit>.ctx` when you need flattened includes for decomp work.
4. Edit the source file with the smallest viable change.
5. Build the single object with `ninja build/GCBE7D/src/<unit>.o`.
6. Re-run `python tools/ai_lookup_symbol.py <symbol>`, `python tools/ai_context.py <symbol>`, or `python tools/ai_match_plan.py <unit>` to confirm the target still resolves and to inspect updated match data.
7. Run `ninja changes` if the work can affect matching or regression state. If `build/GCBE7D/baseline.json` is missing, run `ninja baseline` first.

## Practical Rules

- Prefer the normalized unit name printed by the lookup helpers when duplicate basenames exist.
- Use `build/GCBE7D/report.json` through `ai_context.py` when you need function-level fuzzy-match data.
- For regression checks in automation, use `ninja changes` and `python tools/changes_fmt.py build/GCBE7D/report_changes.json`; avoid interactive `objdiff-cli diff` sessions.
- Use `build/GCBE7D/asm/<unit>.s` when context and current source are not enough to reconstruct the exact function shape.
- Keep code edits narrow and reversible. Avoid unrelated cleanup while matching.
- If a function stops improving after 4 build/measure cycles, record the blocker and move to the next function instead of stalling.

## References

- Read [references/verification.md](references/verification.md) for the default verification sequence and exit criteria.
- Read [references/file-campaign.md](references/file-campaign.md) for file-based autonomous matching loops.
- Read [references/match-style.md](references/match-style.md) for high-signal style rules that improve true matches.

Related Skills

ghidra-workflow

8
from denzi-gh/crashwoc-decomp

Query the local Crash WOC Ghidra project through analyzeHeadless.bat for function lookup, decompilation, disassembly, and datatype inspection.

decomp-match

8
from denzi-gh/crashwoc-decomp

Autonomous matching-decompilation workflow for Crash WOC GameCube units. Use when the agent needs to decomp-match functions in a C source file.

task-pack

8
from denzi-gh/crashwoc-decomp

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

8
from denzi-gh/crashwoc-decomp

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.

split-maintenance

8
from denzi-gh/crashwoc-decomp

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.

project-onboarding

8
from denzi-gh/crashwoc-decomp

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.

build-triage

8
from denzi-gh/crashwoc-decomp

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

8
from denzi-gh/crashwoc-decomp

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.

repo-defining-workflows

9
from wahidyankf/open-sharia-enterprise

Workflow pattern standards for creating multi-agent orchestrations including YAML frontmatter (name, goal, termination, inputs, outputs), execution phases (sequential/parallel/conditional), agent coordination patterns, and Gherkin success criteria. Essential for defining reusable, validated workflow processes.

git-workflow

9
from jkomoros/community-patterns

Git operations and pull request workflows. Create PRs, rebase branches, resolve conflicts, merge to upstream. Use when ready to create PR or when working with git branches and upstream.

git-workflow-helper

9
from davidmatousek/tachi

Automates git workflow tasks including status checks, branch creation, file staging, conventional commit message generation, and pull request creation with gh CLI. Use this skill when you need to commit changes, create PRs, check git status, create branches, push code, or generate commit messages. Ensures proper git workflow and commit standards.

branchless-workflow

9
from jpoutrin/product-forge

Git-branchless stacked diffs workflow patterns and command reference