match-workflow

スター12

フォーク0

更新日2026年3月13日 16:45

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

denzi-gh

denzi-gh/crashwoc-decomp-gc

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Match Workflow

Standard Loop

Resolve the target with python tools/ai_lookup_symbol.py ..., python tools/ai_lookup_unit.py ..., or python tools/ai_context.py ....
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.
Build the context target with ninja build/GCBE7D/src/<unit>.ctx when you need flattened includes for decomp work.
Edit the source file with the smallest viable change.
Build the single object with ninja build/GCBE7D/src/<unit>.o.
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.
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 for the default verification sequence and exit criteria.
Read references/file-campaign.md for file-based autonomous matching loops.
Read references/match-style.md for high-signal style rules that improve true matches.

このリポジトリの他の Skills

同じリポジトリ

task-pack

denzi-gh/crashwoc-decomp-gc

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).

2026-06-0212

decomp-match

denzi-gh/crashwoc-decomp-gc

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

2026-03-3112

agent-orchestration

denzi-gh/crashwoc-decomp-gc

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.

2026-03-3112

ghidra-workflow

denzi-gh/crashwoc-decomp-gc

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

2026-03-3112

build-triage

denzi-gh/crashwoc-decomp-gc

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.

2026-03-1312

project-onboarding

denzi-gh/crashwoc-decomp-gc

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.

2026-03-1312

Match Workflow

Standard Loop

Resolve the target with python tools/ai_lookup_symbol.py ..., python tools/ai_lookup_unit.py ..., or python tools/ai_context.py ....

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.

Build the context target with ninja build/GCBE7D/src/<unit>.ctx when you need flattened includes for decomp work.

Edit the source file with the smallest viable change.

Build the single object with ninja build/GCBE7D/src/<unit>.o.

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.

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 for the default verification sequence and exit criteria.

Read references/file-campaign.md for file-based autonomous matching loops.

Read references/match-style.md for high-signal style rules that improve true matches.

name	match-workflow
description	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.