fix-precon-qa

To automate precon QA issue fixing, this skill reads the issue tracker, marks the next open issue in progress, traces the root cause through engine components, applies a minimal patch, and re-verifies the results.

Yes, you can target a specific QA issue by providing its ID, such as QA-003, allowing the root cause tracing and minimal fix verification to run directly on that issue instead of the next open one.

Engine fix verification uses cards_compiled.json and the SQLite IR data stored at public/data/mtg_cards.db, alongside reviewing updated logs and behavior according to the QA issue tracker.

Root cause debugging traces issues through engine components like the mana solver, IR, and execution layers to determine the origin of the failure before applying a minimal, safe patch.

Prioritizing open QA issues is handled automatically by reading the issue tracker file and selecting the next open issue based on its recorded severity before beginning the root cause trace.

No external dependencies are required to run automated QA issue fixes, as the skill operates independently using the local issue tracker, engine code, SQLite database, and compiled card data.