Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    AI Game Bug Investigation Engineer

    1

    Systematically diagnose game crashes, physics glitches, and networking bugs with evidence-backed QA reports.

    $29.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    AI Game Bug Investigation Engineer

    AI Game Bug Investigation Engineer

    Example session with this skill installed

    Investigate a bug where players fall through the floor in Level 2 after using a dash ability. I've attached a log showing a physics warning and the dash script. Engine is Unity 2022.3 LTS.

    • Read your context and instructions
    • Compiled the ai game bug

    The investigation into the collision failure during the dash state is complete. The evidence suggests a race condition between the character controller's state transition and the physics engine's collision detection during high-velocity frames.

    Game Bug Investigation Report: Floor Collision Bypass

    FieldDetail
    ObservedPlayer character loses collision with floor geometry during 'Dash' ability.
    ExpectedContinuous collision detection (CCD) should prevent floor penetration regardless of velocity.
    ImpactCritical. Players fall out of world bounds, requiring a checkpoint reload.
    EngineUnity 2022.3 LTS (PhysX)
    ClassificationPhysics / Character Movement
    SeverityHigh

    Hypotheses

    High Confidence: The Dash script modifies transform.position directly, bypassing the Physics engine's interpolation and sweeping.
    2.

    Medium Confidence: The character's Rigidbody is set to 'Discrete' collision detection, which fails at the dash velocity (measured at 50 units/s).
    3. Low Confidence: The floor mesh in Level 2 has backface culling issues or missing collider segments.

    Recommended Fix

    Change the dash implementation from direct transform manipulation to Rigidbody.MovePosition or AddForce. Ensure CollisionDetectionMode is set to ContinuousSpeculative during the dash state to handle high-speed tunneling.

    Next steps

    1. Switch the DashController.cs to use physics-based movement instead of transform.Translate.
    2. Verify the fix by running the reproduction steps at 30 FPS to simulate physics lag.
    3. Check all other dash-enabled characters for similar Discrete collision settings.

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

    About this skill

    Finding the root cause of an intermittent game crash or a physics glitch shouldn't feel like guesswork. This skill transforms raw telemetry, messy logs, and vague player reports into rigorous, evidence-backed technical diagnoses for game developers.

    What it does

    • Standardizes reports by converting raw input into structured Observed/Expected/Impact/Scope breakdowns.
    • Formulates hypotheses by ranking potential causes based on confidence levels and available evidence.
    • Isolates root causes through controlled variable testing and comparison of affected versus unaffected builds.
    • Classifies defects across gameplay logic, physics, AI behavior, networking, and rendering categories.
    • Validates fixes with a comprehensive regression test matrix covering edge cases and platform-specific states.

    How it works

    1. Intake: Provide the game version, platform, player actions, logs, or crash dumps.
    2. Investigation: The agent normalizes the report and establishes a minimal reproduction sequence.
    3. Diagnosis: It analyzes stack traces and telemetry to generate a ranked fault tree of potential causes.
    4. Recommendation: You receive a fix strategy including subsystem location, pseudocode, and a rollback plan.

    Frameworks & tools

    Optimized for Unity, Unreal Engine, and Godot workflows. It handles C++ stack traces, Blueprint boundaries, C# scripting backends, and platform-specific logs for mobile, console, and desktop.

    Why this beats prompting it yourself

    Generic prompts often hallucinate engine APIs or miss the nuance of race conditions in multithreaded game loops. This skill enforces strict QA principles, like changing one variable at a time and separating observed facts from hypotheses, ensuring engineering handoffs are actionable.

    Use cases

    • Crash Analysis: Debugging non-deterministic crashes by analyzing memory ownership and lifecycle events.
    • Network Desync: Identifying authority and replication issues in multiplayer gameplay.
    • Progression Blockers: Finding state transition failures in complex quest or save/load systems.
    • Performance Triage: Investigating frame pacing issues or resource leaks using profiler data.

    Known limitations

    Does not perform live memory debugging or real-time code execution. Requires manual provision of logs, telemetry, or source snippets for specific diagnosis.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    Requires manual logs or telemetry. Cannot execute code or attach to a live process. Logic is limited to the accuracy of the provided build and environment details.

    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 buying a skill.

    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 7 days ago

    Permissions

    Read Files
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill is compatible with any LLM-based agent that supports file uploads or text-based logs, and it is pre-configured to understand the specific scripting backends of Unity (C#), Unreal Engine (C++/Blueprints), and Godot.

    You will receive the core logic modules for bug classification, hypothesis generation, and regression testing, along with documentation on how to pipe your logs and telemetry into the agent for the best results.

    The skill uses a structured diagnostic framework to analyze stack traces and player logs, effectively identifying non-deterministic issues like race conditions and memory leaks that generic prompts often overlook.

    No direct integration is required; simply provide the agent with your existing crash dumps, console logs, or profiler data, and it will begin the investigation using its internal QA logic.

    While the agent cannot execute your code or attach a live debugger, it can analyze provided source snippets to suggest specific pseudocode fixes and identify the exact subsystem where the fault lies.

    New in Game Development