Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Autonomous Game QA Testing Agent

    1

    Transform game logs, requirements, and build notes into structured test plans and actionable bug reports.

    $19.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Autonomous Game QA Testing Agent

    Autonomous Game QA Testing Agent

    Example session with this skill installed

    Analyze these logs from Build 0.4.2 where players report a crash when entering the 'Ice Tundra' level. Provide log triage and a structured bug report. [Log: Exception in UnityMain, NullRef at IceLevel.cs:42]

    • Read your context and instructions
    • Compiled the autonomous game qa

    I have analyzed the provided log snippet from Build 0.4.2. The error points to a NullReferenceException during the scene transition lifecycle.

    Log Triage and Bug Report

    Log Triage: Grouped Signatures

    SignatureFrequencyConfidenceSuspected Cause
    NullReferenceException: IceLevel.cs:421 instance providedHighUninitialized reference to the WeatherManager during the OnEnable call in the IceTundra scene.

    Bug Report: GQA-001

    Title: Crash (NullRef) when loading Ice Tundra level
    Severity: Blocker (Prevents progression to Act 2)
    Priority: High
    Status: Reproduction steps proposed
    Environment: Build 0.4.2 (Unity)

    Preconditions:

    1. Player must have completed the 'Mountain Pass' quest.
    2. Character must be equipped with 'Cold Resistance' gear (inferred from scene requirements).

    Reproduction Steps:

    1. Launch Build 0.4.2.
    2. Load a save file at the 'Mountain Pass' exit portal.
    3. Interact with the portal to trigger the 'Ice Tundra' level load.
    4. Observe the application behavior during the loading screen.

    Actual Result: Application freezes and crashes to desktop. Unity log reports NullReferenceException at IceLevel.Start().
    Expected Result: Scene loads successfully and player spawns at the Tundra campfire.

    Evidence:
    Stack Trace: IceLevel.cs:42 inside Start() method calling WeatherManager.Initialize()

    Next steps:

    • Verify if WeatherManager is present in the IceTundra.unity scene hierarchy.
    • Check if the script execution order for IceLevel is set before the WeatherManager initialization.
    • Test if the crash occurs on a clean save versus a loaded save.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Game development teams face a constant struggle to turn chaotic logs, crash traces, and vague player reports into actionable engineering tickets. This skill automates the transformation of raw game telemetry and requirements into structured QA assets. It forces a clear distinction between observed facts and bug hypotheses, ensuring your team stops chasing "ghost" bugs and starts fixing reproducible defects.

    What it does

    • Scope & risk analysis identifies high-risk areas like save integrity, progression blockers, and multiplayer stability based on change logs.
    • Test matrix generation builds atomic, reproducible test cases covering smoke tests, mechanics, UI, and performance budgets.
    • Log triage groups error signatures, identifies root-cause stack traces, and proposes experiments to confirm hypotheses.
    • Reproduction protocols defines exact sequences, preconditions, and environment states needed to trigger intermittent failures.
    • Bug report automation generates tracker-ready reports with severity rankings, reproduction frequency, and evidence links.
    • Release readiness reporting provides a data-driven go/no-go summary based on risk-weighted coverage and blocker status.

    How it works

    1. Input artifacts like requirements, crash logs, or build notes are analyzed to establish the testing context.
    2. Select mode by requesting a specific output such as test_plan, log_triage, or bug_reports.
    3. Execute workflow where the agent maps evidence to hypotheses and generates structured Markdown deliverables.

    Frameworks & tools

    Works with any game engine including Unity, Unreal Engine, Godot, and Roblox. Processes standard logs, stack traces, and telemetry excerpts from platform-specific crash reporters.

    Why this beats prompting it yourself

    Generic prompts often invent test results or hallucinate reproduction steps that don't exist in the logs. This skill enforces strict evidence-led reasoning, redacts sensitive tokens, and uses specialized game QA severity logic that distinguishes between cosmetic issues and progression blockers.

    Use cases

    • Generating a smoke test suite for a new build on Steam or mobile.
    • Analyzing a high-volume crash log from a recent patch to find the first meaningful error.
    • Drafting professional bug reports from raw notes taken during a playtest session.
    • Evaluating release readiness by calculating execution coverage against a planned test inventory.

    Known limitations

    Does not execute code or interact directly with live game builds. Coverage metrics rely entirely on user-provided execution data.

    Cannot execute tests or access live builds. Coverage calculations require manual input of execution status. Requires logs to be provided for triage.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    Permissions

    Read Files
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between raw data and engineering tasks by converting chaotic crash logs, build notes, and playtest feedback into professional, structured QA documentation like test plans and bug reports.

    While it works with any engine (Unity, Unreal, Godot, etc.), the skill requires you to provide the text-based logs, requirements, or telemetry data; it does not directly hook into your game's source code or live build.

    Unlike generic prompts, this skill uses evidence-led reasoning to prevent 'hallucinated' reproduction steps and applies specific game-industry severity logic to distinguish between minor UI glitches and critical progression blockers.

    Upon purchase, you receive the full agent configuration and workflow instructions designed to handle game-specific artifacts like stack traces, change logs, and test matrices.

    Yes, you can select specific modes such as `log_triage` for debugging crashes, `test_plan` for new feature coverage, or `bug_reports` for converting playtest notes into tracker-ready tickets.

    New in Game Development