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.
Best use case
build-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using build-triage 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/build-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How build-triage Compares
| Feature / Agent | build-triage | 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?
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.
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
# Build Triage ## Compile Failures For broad compile trouble, start with: - `python tools/triage_build.py` Useful variants: - `python tools/triage_build.py --match ai` - `python tools/triage_build.py --all-failures` - `python tools/triage_build.py --list` For targeted iteration, build just the one object: - `ninja build/GCBE7D/src/<unit>.o` ## Progress and Regressions Use the standard report commands: - `ninja progress` - `ninja baseline` - `ninja changes` If you want formatted regression output directly: - `python tools/changes_fmt.py build/GCBE7D/report_changes.json` Do not run interactive `objdiff-cli diff` sessions from automation. They do not terminate on their own. Use the file-based report flow above, or direct `objdiff-cli report changes ... -o <file>` if you need raw JSON output. ## Working Pattern 1. Reproduce the failure or regression on the narrowest useful target. 2. Use `triage_build.py` when header or type issues make the first failing object unclear. 3. Use `python tools/ai_match_plan.py <unit-or-path>` when a file-level matching campaign stalls and you need the next actionable function. 4. Use `ninja changes` before wrapping up if matching behavior may have moved. 5. Use `build/GCBE7D/report.json` or `python tools/ai_context.py <unit>` when you need unit-level match data.
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.
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.
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.
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.
Goal: Build an LLM-based RAG App
Here is the MVP Implementation Plan.
performing-web-application-vulnerability-triage
Triage web application vulnerability findings from DAST/SAST scanners using OWASP risk rating methodology to separate true positives from false positives and prioritize remediation.
performing-malware-triage-with-yara
Performs rapid malware triage and classification using YARA rules to match file patterns, strings, byte sequences, and structural characteristics against known malware families and suspicious indicators. Covers rule writing, scanning, and integration with analysis pipelines. Activates for requests involving YARA rule creation, malware classification, pattern matching, sample triage, or signature-based detection.
performing-alert-triage-with-elastic-siem
Perform systematic alert triage in Elastic Security SIEM to rapidly classify, prioritize, and investigate security alerts for SOC operations.