replay-debugging

Name: replay-debugging
Availability: InStock
Author: CHRONiiC

Retrieves and analyzes a single Lo rproduction turn via the tcg-replay CLI.

Updated May 14, 2026

Search Tags:#lorcana #production triage #replay debugging #json patches #game state tracing #tcg-replay #ml-ready traces

Ready to run

npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill replay-debugging-chroniicallydiistracted

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: replay-debugging
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.agents/skills/replay-debugging
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill replay-debugging-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Replay debugging converts a player-reported Lorcana turn into a concrete, step-by-step evidence trail you can inspect, so you can pinpoint which card definitions, moves, logs, and state patches were involved.

Core Features & Use Cases

Production replay ingestion: Pulls a specific turn from a real game via the tcg-replay CLI using a provided replay id and 1-based turn number.
Evidence-first turn forensics: Extracts the touched cards list with on-disk file paths, then prints the reconstructed pre-turn match state plus the ordered steps (moves, engine logs, and JSON patches).
Bug triage workflow support: Produces the artifacts needed to reproduce the issue as a hypothesis and hand off to card-specific validation or test generation.

Quick Start

Use the replay-debugging skill to run tcg-replay for the provided gameId and turn number, then read the CARDS INVOLVED section to open only the relevant card files before forming your hypothesis.

Frequently Asked Questions about replay-debugging

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

FAQPage Schema

How do I trace a Lorcana game state from a production replay to find a bug?▼

To trace Lorcana game state, run the tcg-replay CLI with a provided replay id and 1-based turn number. This extracts an evidence trail containing touched card file paths, reconstructed pre-turn match state, and ordered per-step moves, engine logs, and JSON patches.

What are JSON patches in replay debugging and how do they help with game state tracing?▼

JSON patches in replay debugging are structured per-step state changes extracted from a Lorcana replay turn. They provide concrete evidence of state transitions alongside engine logs and moves, enabling precise identification of what occurred in-game for triaging player bug reports.

Can I use production replay ingestion to triage player bug reports tied to a specific game id?▼

Yes, production replay ingestion pulls a specific turn from a real game using the tcg-replay CLI. It requires a reported game id and a suspect 1-based turn number to reconstruct the match state and identify involved card files for bug triage.

How do I identify which card files were touched during a specific Lorcana turn?▼

You identify touched card files by running the replay-debugging process and reading the structured CARDS INVOLVED section. This output lists the specific on-disk file paths for all card definitions affected during the target replay turn.

What do I need to run tcg-replay for Lorcana production triage?▼

You need a real game id and a suspect 1-based turn number from a player bug report to run tcg-replay. The CLI uses these parameters to ingest the production replay and generate structured output sections including involved cards, pre-turn match state, per-step moves, logs, and JSON patches.

Are there limitations when using replay debugging for Lorcana bug triage?▼

Replay debugging is limited to analyzing a single specified turn per replay id, requiring you to know the exact 1-based turn number beforehand. It produces evidence for hypothesis testing rather than automatically fixing card definitions or resolving the bug directly.