qa-review-batch

Automate batch QA reviews of precon game logs and generate centralized issue logs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill qa-review-batch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-review-batch
Source: https://github.com/Tomoda826/mtg-goldfisher/tree/main/.claude/skills/qa-review-batch
Command: npx skills add https://github.com/Tomoda826/mtg-goldfisher --skill qa-review-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-driven batch QA reviews of precon game logs to identify quality issues without manual per-turn inspection.

Core Features & Use Cases

  • Reads per-game Markdown logs and evaluates decks against 4 predefined criteria, logging issues to PRECON_QA_ISSUES.md.
  • Supports batch targeting with optional --batch parameter and automatic discovery from results/qa_tracker.json.
  • Provides deduplicated issue tracking and centralized reporting for reviewer efficiency.

Quick Start

Run the review on the next pending batch to generate a consolidated issue log and updated tracker.

Frequently Asked Questions about qa-review-batch

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

FAQPage Schema
How do I automate batch QA reviews of precon game logs?▼

Batch QA reviews of precon game logs automatically process Markdown files against 4 predefined criteria, generating centralized issue logs. This eliminates manual per-turn inspection by updating qa_tracker.json and writing deduplicated issues to PRECON_QA_ISSUES.md.

What is the best way to track log issues across multiple precon decks?▼

Tracking log issues across multiple precon decks is best handled by centralized reporting tools that batch process game logs and write deduplicated issues to a Markdown file. This approach updates a JSON tracker automatically to maintain reviewer efficiency.

How do I run batch processing on pending precon game logs?▼

Running batch processing on pending precon game logs requires executing the review with an optional --batch parameter. The system automatically discovers pending batches from qa_tracker.json and generates a consolidated issue log upon completion.

Can I use markdown game logs for automated QA issue tracking?▼

Markdown game logs are fully supported for automated QA issue tracking. The system reads per-game Markdown files, evaluates decks against predefined criteria, and logs deduplicated issues directly into a centralized Markdown report for reviewer efficiency.

Does batch QA review support automatic discovery of pending games?▼

Batch QA review supports automatic discovery of pending games through the results/qa_tracker.json file. You can also manually target specific groups of precon game logs using the optional --batch parameter for more controlled processing.

Why does manual per-turn inspection fail for post-game QA workflows?▼

Manual per-turn inspection fails for post-game QA workflows across multiple precon decks because it cannot efficiently scale. AI-driven batch QA reviews solve this by evaluating logs against 4 criteria and generating centralized issue logs without manual intervention.