Menu
Analyze the most recent game log to identify card effect issues, gameplay bugs, and missing implementations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | scan-match |
| description | Analyze the most recent game log to identify card effect issues, gameplay bugs, and missing implementations. |
| model | sonnet |
| effort | medium |
Analyze the most recent game log to identify card effect issues, gameplay bugs, and missing implementations.
Read game_log.txt from the project root. It may be large — read it in chunks using offset/limit (500 lines at a time). Read the entire file; do not skip sections.
Scan for the following categories of issues:
>> WARNING: MISSING EFFECT indicate cards played whose effect_ids are not covered by triggered_abilities, keywords, or equip fields.[TRIGGER] lines show effects that fired. Check whether they make sense:
[DAMAGE] and [DEATH] lines show combat results. Check for:
[BOARD] snapshots[BOARD] snapshots show creature stats. Check for:
Read development-artifacts/unfixed_card_effects.md and check:
Present findings organized as:
New Missing Effects — Cards with missing effects NOT already tracked in unfixed_card_effects.md. For each, include the card name, definition_id, uncovered effect_ids, and rules_text. These are actionable — suggest using /fix-card-effect <card_name> for each.
Known Missing Effects — Cards with missing effects that ARE already tracked. Just list the names briefly so the user knows they appeared in the match.
Gameplay Bugs — Any combat, trigger, board state, or event ordering issues found. Include the relevant log lines and explain what looks wrong.
Summary — A brief overall assessment: how many turns played, who won, how many unique issues found.
Debug a bug using the user's description and the match log file from the most recent game.
Audit cards for data accuracy and engine correctness. Supports single-card audit (compare against UESP wiki, verify engine ops/targets/families, report PASS or NEEDS_FIX) or full-catalog batch audit with progress tracking.
Investigate and fix a card whose in-game effect is not working as described.
Add a reusable UI pattern to the catalog. Use when a new UI feature has been built and should be documented for future reuse — e.g. "add this animation pattern", "catalog this UI flow". Takes a description of the pattern and the relevant files.
Find a reusable UI pattern from the catalog given a description of what you need. Use when implementing a new card or mechanic and you want to check if an existing UI pattern applies — e.g. "I need an arrow from one creature to another", "show damage after an animation", "defer an effect until a visual plays".
Configure a test match scenario for manual gameplay testing. Use when user wants to test a card, mechanic, keyword, or interaction in-game — e.g. "test veteran", "set up a match with treasure hunt cards", "I want to try Consume". Creates a JSON config in data/test_match_configs/ so the user can press ? on the Match button to pick and launch it.