skills.rest
OpenGGF
OpenGGFOFFICIAL
Explore all skills by this author →
WebsiteGitHub

s1-trace-replay

Compare Sonic 1 engine traces against recorded reference data to identify physics divergences.

6|1|Updated Jan 16, 2013
Search Tags:#regression testing#sonic#trace replay#divergence analysis#bizhawk#physics validation
One-click install
npx skills add https://github.com/OpenGGF/OpenGGF --skill s1-trace-replay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: s1-trace-replay
Source: https://github.com/OpenGGF/OpenGGF/tree/main/.claude/skills/s1-trace-replay
Command: npx skills add https://github.com/OpenGGF/OpenGGF --skill s1-trace-replay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you record, replay, and analyze Sonic 1 trace data so you can verify engine physics against reference runs and pinpoint divergences quickly.

Core Features & Use Cases

  • Trace Recording: Capture BizHawk playthroughs and export physics, metadata, and auxiliary event logs.
  • Replay Testing: Run Maven trace tests to compare engine output against reference traces for GHZ1 and MZ1.
  • Divergence Analysis: Read JSON reports and auxiliary logs to isolate the first error and understand cascading mismatches.
  • Use Case: A contributor updating collision code can rerun the full trace workflow and confirm whether the engine still matches the reference behavior.

Quick Start

Use the s1-trace-replay skill to record, validate, and compare a Sonic 1 trace for ghz1 or mz1 and interpret the latest divergence report.

Frequently Asked Questions about s1-trace-replay

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

FAQPage Schema
How do I verify Sonic 1 engine physics against recorded reference traces?▼

Verify Sonic 1 physics by recording BizHawk playthroughs and running Maven trace tests to compare engine output against reference traces for GHZ1 and MZ1 regression analysis.

What is trace replay divergence analysis for Sonic 1?▼

Divergence analysis reads JSON reports and auxiliary event logs to isolate the first physics error and understand cascading mismatches against reference runs in Sonic 1.

Can I use BizHawk .bk2 movies for Sonic 1 trace recording?▼

Yes, BizHawk .bk2 movies are required to capture playthroughs and export physics, metadata, and auxiliary event logs for Sonic 1 trace validation and replay testing.

How do I run Maven trace tests to compare Sonic 1 engine output?▼

Run Maven trace tests to compare Sonic 1 engine output against reference traces, generating divergence reports with auxiliary event context for regression validation.

Do I need CSV and JSON metadata for Sonic 1 trace validation?▼

Yes, Sonic 1 trace validation requires CSV and JSON metadata validation alongside recorded .bk2 movies and trace output artifacts to accurately identify physics divergences.

Related Skills

Explore More Software Engineering Skills→
OpenGGFOpenGGF
6

s1-retro-trace

Record Sonic 1 physics traces for Java replay verification.

Official
Intermediate
dyyounggdyyoungg

debug-distributed-hang

Diagnose distributed hangs in multi-GPU SGLang deployments using per-rank traces, NCCL logs, and CUDA core dumps.

Community
Advanced
rajnishkhatrirajnishkhatri

governance-trace-audit

Audit AgentsFramework Langfuse traces against governance triangle compliance rules.

Community
Advanced
leocostaleocosta
4

audit-grounding

Compare diffs against CONTEXT.md, docs/adr, and knowledge base for semantic divergences.

Community
Intermediate