Three shifts in your day.
Repros run themselves
Through the Unreal MCP, Claude can attempt a reported repro in the editor itself — load the map, perform the steps, capture the state. "Could not reproduce" gets a lot rarer.
Crashes arrive pre-triaged
Every crash log comes back decoded: what failed, where, whether it's a known issue, and which change likely introduced it — before an engineer ever gets pinged.
Your reports become gold-standard
Claude turns raw session notes into structured, engineer-ready bugs — versioned, symbolicated, deduped against the existing database. Ping-pong dies.
The playbooks you'll use most.
Browse all QA skills in the Library →
Runs Unreal's Automation framework with our filters — full suite or one system — and reads the results back in plain English. Better: hand it a bug you just caught manually, and it writes the regression test that makes sure it never comes back.
The suite grows a little with every bug you find. That's how manual QA compounds into automated coverage.
Paste any crash, ensure, or log excerpt. Claude symbolicates it, identifies the failing system, checks it against our known-issues table, and tells you whether it's new, a dupe, or a regression — plus which recent changes are the likely suspects.
You stop being a courier between the crash folder and the engineering channel. You send diagnoses, not dumps.
Give Claude the repro steps and it drives the editor: loads the map, performs the sequence, queries actor state, captures logs and screenshots at the moment of failure. It can also re-verify a fix the moment engineering lands it — closing the loop the same day.
Which build has which changes, why the nightly failed, whether the fix you're waiting on is actually in the package you're testing. Claude reads build logs and changelists so "what build am I even on?" always has a fast, accurate answer.
Our full pre-release gauntlet — packaging settings, platform requirements, cert checks, smoke passes — as a checklist Claude walks and evidences item by item. Release candidates get boringly predictable, which is exactly what you want.
The rest of the job gets faster too.
Reports that write themselves
Raw session notes in, structured bugs out — repro steps, expected vs actual, build number, severity rationale, deduped against what's already filed.
Test plans from specs
Hand Claude a feature spec and get a draft test plan back: happy paths, edge cases, and the nasty interaction cases humans forget until Friday at 6pm.
Trend spotting
"What are our flakiest tests this month? Which systems generate the most regressions?" Claude reads across the bug database and tells you where the fire actually is.
Every mystery you solve becomes a lookup.
Cracked a weird failure that took two days? Add it to log-and-crash-triage's known-issues table with one sentence: "add this crash signature and fix to the skill." The next time it appears, triage takes ninety seconds — for anyone on the team. See exactly how →
Every crash, not just the one on your desk.
Right now log-and-crash-triage works on logs you have locally. Connect Sentry — which has a first-class Unreal SDK, so crashes from real builds on real machines all land in one dashboard — and the same skill starts answering questions you currently can't: what's the top new crash since Thursday's build, is this regression or a known issue, how many players hit it, which changelist looks responsible.
Pair it with Jira and the loop closes: triage the crash, file the ticket, link the evidence, without leaving the session. Both, with commands →