Fix failing scenario tests by analyzing open issues and oracle texts.
npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill fix-scenarios
Please help me install this Agent Skill. Skill: fix-scenarios Source: https://github.com/Tomoda826/mtg-goldfisher/tree/main/.claude/skills/fix-scenarios Command: npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill fix-scenarios
Picks the next open issue from docs/SCENARIO_ISSUES.md, deeply analyzes each affected scenario against oracle text, fixes the test or engine (one issue per run), and verifies the fix.
Run the fix-scenarios workflow to read docs/SCENARIO_ISSUES.md, pick the next OPEN issue, implement the fix, and validate it with existing or new scenarios.
High-intent search queries and answers about installing and using this skill.
To automatically fix failing scenario tests, this Skill reads open issues from docs/SCENARIO_ISSUES.md, analyzes affected scenarios against oracle texts, applies validated changes to tests or engine logic, and verifies the fixes end-to-end.
Scenario test automation determines whether to fix the test or engine logic by deeply analyzing each affected scenario against oracle text and engine IR, isolating the root cause before applying minimal validated changes to restore correct behavior.
The best way to validate fixes for scenario tests is to create and run end-to-end test scenarios that prove the fix works, using the repository's standard execution scripts to verify the updated scenario JSONs and engine logic.
Yes, you need a specific issue tracker format: the workflow reads open issues directly from the docs/SCENARIO_ISSUES.md file in your repository to select the highest-impact failing scenario test to process.
No, you cannot use this automated scenario runner to fix multiple test issues at once; it processes exactly one open issue per run to ensure minimal, validated changes and clear documentation in SCENARIO_ISSUES.md.
Your scenario test fix needs new test scenarios to ensure changes are supported by end-to-end validation, proving the fix works and adequately covers edge cases before updating the issue tracker documentation.
fmoda3Analyze inputs and symptoms to identify root causes of system failures.
LanternOpsAutomates UI, API, and agent feature verification using Playwright MCP and diagnostic logs.
TheCardGoatConvert Lorcana player bug reports into failing simulator tests and engine fixes.
cristian-robertReplay failing Playwright tests in a traceable browser session to diagnose failures.
