progress

Summarize RB3 decomp build report metrics per category from report.json.

4|Updated Mar 19, 2026

Search Tags:#engineering #code-analysis #progress #porting #build-report #rb3 #decomp

Ready to run

npx skills add https://github.com/freeqaz/rb3 --skill progress-freeqaz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: progress
Source: https://github.com/freeqaz/rb3/tree/main/.claude/skills/progress
Command: npx skills add https://github.com/freeqaz/rb3 --skill progress-freeqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RB3 decomp projects need visibility into progress across categories; this skill summarizes the build report to highlight remaining work and category gaps.

Core Features & Use Cases

Per-category progress summaries sourced from the build report (report.json) and driven by configure.py's progress_category rules.
In-scope rollups for the port surface (game and engine) to guide prioritization.
Clear targets for decomp work by exposing counts, percentages, and remaining bytes of code.

Quick Start

Refresh the report then run the provided snippet to display per-category progress and the in-scope totals.

Frequently Asked Questions about progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check RB3 decomp progress across different categories?▼

RB3 decomp progress is tracked by summarizing build report metrics from report.json per category. This provides per-category counts, percentages, and remaining bytes of code to reveal remaining work across game and engine port surfaces.

What build report fields are needed to show decomp progress?▼

Decomp progress requires the categories[].measures field in the build report containing matched_functions, total_functions, matched_code, total_code, and fuzzy_match_percent percentages to calculate matched and remaining work.

Can I use this to identify remaining code gaps in a decompilation project?▼

Yes, identifying remaining code gaps is achieved by exposing counts, percentages, and remaining bytes of code per category. It applies across game and engine port surfaces to highlight target areas for decomp work.

Do I need configure.py to populate category data for build reports?▼

Yes, configure.py is required to populate the progress_category rules and category data. This setup must be completed before analyzing the build report JSON to ensure accurate decomp progress summarization.

Where does the build report JSON need to be located for progress tracking?▼

The build report JSON must be located at build/SZBE69_B8/report.json for progress tracking. Access to this file path is required to extract the per-category decomp metrics and calculate rollups.