source-command-triage-player-report

Triage Lorcana player bug reports into failing repro tests and minimal fixes.

Updated May 14, 2026
One-click install
npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-triage-player-report-chroniicallydiistracted
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-triage-player-report
Source: https://github.com/chroniicallydiistracted/LorcanaChamp/tree/main/references/lorcana-simulator/.agents/skills/source-command-triage-player-report
Command: npx skills add https://github.com/chroniicallydiistracted/LorcanaChamp --skill source-command-triage-player-report-chroniicallydiistracted

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill triages a player bug report for the Lorcana simulator and converts it into a rules-grounded, reproducible failing test before implementing the minimal engine/card fix.

Core Features & Use Cases

  • Linear-aware ingestion: Pulls and normalizes a Linear issue’s title, description, and context when a Linear URL is provided, while posting concise progress updates.
  • Evidence-backed triage: Optionally pulls production replay evidence for a specific gameId and turn, using it to refine suspect steps and touched-card candidates.
  • Deterministic validation and TDD: Resolves cards, cross-checks official rules, generates a minimal failing repro test, implements the fix, and verifies with targeted tests and CI checks.
  • Minimal, safe change discipline: Enforces an explicit no-repro/no-fix workflow and uses precedence rules to resolve conflicts between evidence and skill outputs.

Quick Start

Use the source-command-triage-player-report skill to triage a player’s Linear issue or raw bug report, then produce a failing test and a verified minimal fix in the simulator.

Frequently Asked Questions about source-command-triage-player-report

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

FAQPage Schema
How do I fix a Lorcana simulator bug report by generating a failing repro test?▼

To fix a Lorcana simulator bug report, this Skill validates referenced cards, cross-checks official rules, and encodes the issue as a failing repro test before implementing a minimal engine fix and verifying it with targeted tests and CI.

Can I triage a Linear issue URL and pull replay evidence for a Lorcana card validation bug?▼

Yes, you can triage a Linear issue URL by pulling and normalizing its context, and optionally pull production replay evidence for a specific gameId and turn to refine suspect steps and touched-card candidates during card validation.

What is the workflow for turning a raw player bug report into a verified engine fix?▼

The workflow follows an eight-step sequence: ingest the report, pull replay evidence when available, resolve cards deterministically, interpret rules, generate a failing test, implement a minimal fix, and verify with targeted tests and repo CI.

Does the bug triage process enforce a no-repro no-fix discipline for game engine issues?▼

Yes, the bug triage process enforces an explicit no-repro no-fix workflow, requiring a failing repro test to be generated before any minimal engine or card fix is implemented and verified.

How does replay debugging handle conflicts between production evidence and card validation rules?▼

Replay debugging resolves conflicts between production evidence and card validation rules by using precedence rules, ensuring that the deterministic card resolution and official Lorcana rules cross-check remain grounded during the minimal fix implementation.

Do I need a Linear integration to triage player reports for the Lorcana simulator?▼

No, Linear integration is optional for triaging player reports; the Skill accepts raw bug reports directly but can also pull and normalize Linear issue titles, descriptions, and context when a URL is provided.