القائمة
Check the latest game log for evidence of a specific issue described by the user.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | game-log |
| description | Check the latest game log for evidence of a specific issue described by the user. |
Check the latest game log for evidence of a specific issue described by the user.
$ARGUMENTS — Either a specific issue to investigate (e.g., "Morkul Gatekeeper didn't use its summon effect", "Guard was ignored", "creature had wrong stats after buff") or a general request like "summarise the last game".
If the request is a general summary (no specific bug), skip Steps 2-4 and instead provide: match duration (turns), key plays per player, board swings, final state, and any warnings logged. Keep it concise.
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.
Based on the user's description, search the log for relevant evidence. Use the log format to guide your search:
[BOARD] — Board state snapshots at the start of each turn, showing creature stats and HP[PLAY] — A card was played from hand[SUMMON] — A creature entered a lane[TRIGGER] — An effect fired (shows family, effect op, and target)[DAMAGE] — Damage was dealt (shows source, target, amount)[DEATH] — A creature was destroyed[DRAW] — A card was drawn[RUNE] — A rune was broken[PROPHECY] — A prophecy window opened[MAGICKA] — A player gained or spent magicka>> WARNING: MISSING EFFECT — A card's effect_ids are not covered by triggered_abilities[TRIGGER] line followed for an expected effect[TRIGGER] fired but targeted the wrong thing[BOARD] snapshots that don't add up given prior eventsPresent your findings concisely:
Relevant log lines — Quote the specific lines that show the issue (or the absence of expected lines). Include surrounding context so the user can understand the sequence of events.
Analysis — Explain what the log shows happened vs what should have happened, based on the user's description.
Verdict — State clearly whether the log confirms the reported issue or not. If the evidence is ambiguous, say so and explain why.
If the log confirms a bug with a specific card's effect (wrong trigger, wrong target, wrong values), invoke the /fix-card-effect skill with the card name and a summary of what went wrong (derived from your analysis above).
If the bug is a system-level issue (e.g., missing win condition check, incorrect turn sequencing, broken rune logic) rather than a card-specific effect, investigate and fix the relevant engine code directly instead of using /fix-card-effect.
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.