replay-debugging

Name: replay-debugging
Availability: InStock
Author: TheCardGoat

Convert a Lorcana replay turn into a file-anchored debugging trace.

14|5|Updated Mar 16, 2026

Search Tags:#lorcana #triage workflow #replay debugging #json patches #game engine tracing #tcg-replay cli #LLM evidence

Ready to run

npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill replay-debugging

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replay evidence is hard to turn into concrete, file-anchored explanations when a player reports a bug and you need to know what the engine actually did on a specific turn.

Core Features & Use Cases

Download and inspect a production turn: Pull a single Lorcana replay turn and reconstruct the match-state context before the turn.
Card-level traceability: Identify exactly which card instances were touched during that turn, including the on-disk file paths for the card definitions.
Deterministic, step-by-step debugging: Produce a trace of moves, engine logs, and JSON patches for every step in the turn so you can pinpoint where behavior diverged.

Quick Start

Use the replay-debugging skill with a real replay id and turn number to generate a structured trace you can use to validate which cards and steps caused the reported issue.

Frequently Asked Questions about replay-debugging

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

FAQPage Schema

How do I debug a specific turn from a Lorcana game replay?▼

Yes, replay debugging identifies exactly which card instances were touched during a turn and provides their on-disk file paths. It outputs deterministic, step-by-step moves alongside engine logs and JSON patches to pinpoint where behavior diverged.

What is the best way to triage player-reported bugs using game engine tracing?▼

Yes, replay debugging uses the tcg-replay CLI, which requires a valid replay-id and a specific 1-based turn number as input. You invoke it with these two parameters to pull the production replay data and output the structured debugging trace.

How do I get JSON patches for a specific Lorcana replay turn?▼

To get JSON patches for a Lorcana replay turn, invoke the tcg-replay CLI with the replay-id and the 1-based turn number. The skill outputs the step-by-step move trace, engine logs, and the corresponding JSON patches for every step in that turn.

Why does game engine behavior diverge from expected rules during a replay?▼

Game engine behavior diverges when specific move steps or card interactions trigger unexpected logic. By generating a deterministic, step-by-step trace with engine logs and JSON patches for the targeted turn, you can pinpoint the exact step where the divergence occurred.