game-smoke
Skill0 starsChanged 3 days agoMITView on GitHub
Use when a Unity 6 mobile game needs checking on a player build - before saying a visual or UI change is done, after changing a screen or layout, before a release, or when asked for a smoke check, a device check or a screenshot of the game on Android or iOS. Runs in a subagent that does not see this conversation; pass the platform and the screen that changed as the argument.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- szmidtpiotr/ClaudeCode-Toolstheir own version, first seen Jun 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- szmidtpiotr/ClaudeCode-Tools★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- compass-kit/CLAUDE.mdCLAUDE.md
- unity-kit/CLAUDE.mdCLAUDE.md
- backend-new-projectSkill
- cmp-backendSkill
- cmp-code-rulesSkill
- cmp-commitSkill
- cmp-design-rulesSkill
- cmp-design-to-codeSkill
- cmp-detektSkill
- cmp-featureSkill
- cmp-gatesSkill
- cmp-maestroSkill
- cmp-new-projectSkill
- cmp-testingSkill
- cmp-verifySkill
- game-balanceSkill
- game-briefSkill
- game-lookSkill
- game-new-projectSkill
- game-releaseSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Run git status --short at the start and list under Findings only the files that changed during the run.
- Distinctive: line 37
Only a PNG counts: the editor's Game view, its Simulator view, Play mode, a clean compile and passing tests are not evidence and never …
- Very specific: line 40
When no PNG can be produced, the task is not done: the report's Visual line says NOT DONE and names the step and the error that blocked it.
- Very specific: line 64
Not a Unity project, or a version not starting with 6000.: stop, final message NOT ASSESSED with the reason, write nothing.
- Very specific: line 67
When Temp/UnityLockfile exists the project is open in the Unity editor.
- Distinctive: line 94
Always build; an older APK or app says nothing about the current code.
- Very specific: line 118
Run every adb and simctl step with a 60 s limit by prefixing it with perl -e 'alarm 60.
- Distinctive: line 180
Prefer a simulator this run boots.
- Distinctive: line 203
Wait at least 10 seconds after launch before the first capture.
- Distinctive: line 232
Run each on each platform, and cite the PNG behind every visual result.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Game smoke
You run in your own subagent. The session that called you sees only your final report, not your
tool output, and you did not see its conversation. If you cannot fork, run this skill's steps
yourself in the current session. You report; you do not fix. Do not edit tracked
project files; reports go under qa/, build output under Builds/. Unity itself rewrites some
tracked files (for example under Assets/Settings) when tests and builds run; that is expected.
Run git status --short at the start and list under Findings only the files that changed during
the run; leave them, do not revert or commit them.
The visual rule
A visual task is not done without a screenshot.
Evidence is a PNG captured from a device or simulator, then read and retained:
- Captured from a player build running on an Android device or emulator or an iOS simulator, with the commands in section 4.
- Read: open the PNG with the Read tool and write down what is on screen.
- Retained in
qa/evidence/<platform>/and cited by path in the report.
The PNG must show the screen that changed. A launch screenshot proves nothing about a screen three taps in, so navigate there (section 5, Tap) and capture it.
The device run happens now, in this run. When no device is running, boot an emulator or a simulator yourself (section 4). Only a PNG counts: the editor's Game view, its Simulator view, Play mode, a clean compile and passing tests are not evidence and never appear as visual results in the report.
When no PNG can be produced, the task is not done: the report's Visual line says NOT DONE and
names the step and the error that blocked it.
A still shows layout, clipping, overflow, alignment, colour and legibility. It does not show timing,
animation feel or audio; list those under Human checks.
Results
- Each check gets one of:
PASS,WARN,FAIL,NOT RUN(the check could not be carried out; say why),NOT ASSESSED(the data needed to judge it is missing),n/a(does not exist on this platform). NOT RUNandNOT ASSESSEDnever count as passed.
1. Input and project
Caller's request: "$ARGUMENTS"
androidorioslimits the run to that platform; neither means both. The rest names the screen or change to check. The project is the current directory unless the request gives a path.Assets/andProjectSettings/must both exist. Read the version:sed -nE 's/^m_EditorVersion: *([^ ]+).*/\1/p' ProjectSettings/ProjectVersion.txtNot a Unity project, or a version not starting with
6000.: stop, final messageNOT ASSESSEDwith the reason, write nothing.- Editor binary (
$UNITYbelow):$UNITY_EDITOR, else/Applications/Unity/Hub/Editor/<version>/Unity.app/Contents/MacOS/Unity. - When
Temp/UnityLockfileexists the project is open in the Unity editor. Never kill Unity. Stop before tests and builds, write no report, and send the final message withVerdict: NOT ASSESSED,Visual: NOT DONE - close the Unity editor and run again, and theCaller:line of section 6. A build script'sSKIP:for the same lockfile is the same stop. <run>isdate +%F, with-2,-3appended whenqa/smoke-<run>.mdalready exists. Thenmkdir -p Builds/logs qa/evidence/android qa/evidence/ios.- Unity builds can pass ten minutes: run every Unity, build-script and
xcodebuildcommand in the background and wait for it to exit. One at a time; Unity cannot open a project twice.
2. Tests
EditMode exactly as below (no -quit; Unity exits by itself):
rm -f Builds/editmode.xml
"$UNITY" -batchmode -projectPath . -runTests -testPlatform EditMode -testResults Builds/editmode.xml -logFile Builds/logs/editmode.log
grep -m1 '<test-run' Builds/editmode.xmlThen PlayMode: the same commands with -testPlatform PlayMode, Builds/playmode.xml and playmode.log.
For each, read total and failed on that line. failed above 0: FAIL. total 0: NOT ASSESSED. No XML:
FAIL with the first error CS line of the log, or NOT RUN with the last log lines when there is none.
A test failure does not stop the run.
3. Build
Always build; an older APK or app says nothing about the current code.
With ~/.claude/skills/game-new-project/scripts/ present, run build-android.sh <projectDir> and
build-ios.sh <projectDir>. They end in OK:, FAIL: or SKIP:. SKIP: exits 0 but built nothing:
that is NOT RUN with its reason, and that platform's device checks are NOT RUN.
Otherwise follow build without scripts; without
Assets/Editor/Build/BuildScript.cs, Build is NOT RUN.
A failed build is FAIL; that platform's device checks are NOT RUN.
4. Install, launch, capture
The APK is the path in the OK: APK line (or the -cmposeOut path). The iOS app is
find Builds/ios-dd/Build/Products/Debug-iphonesimulator -maxdepth 1 -name '*.app'.
Android
ANDROID_HOME is often unset and adb, emulator and aapt2 are often not on PATH. Set
ANDROID_HOME="${ANDROID_HOME:-$HOME/Library/Android/sdk}" and call $ANDROID_HOME/platform-tools/adb,
$ANDROID_HOME/emulator/emulator and $ANDROID_HOME/build-tools/<version>/aapt2, where <version>
is the newest directory in $ANDROID_HOME/build-tools (ls "$ANDROID_HOME/build-tools" | sort -V | tail -1).
Below, adb, emulator and aapt2 stand for those full paths. Every adb command names its serial.
Run every adb and simctl step with a 60 s limit by prefixing it with
perl -e 'alarm 60; exec @ARGV' -- (perl ships with macOS; timeout does not). It kills the
command after 60 s with exit status 142, and redirects such as > file still work, for example
perl -e 'alarm 60; exec @ARGV' -- xcrun simctl uninstall <udid> <bundleId>. A capture counts as
an adb step, for example
perl -e 'alarm 60; exec @ARGV' -- adb -s <serial> exec-out screencap -p > qa/evidence/android/<run>-01-launch.png.
Below, adb and
xcrun simctl steps are shown without the prefix. Not the emulator or bootstatus boot, and not
wait-for-device, which you poll instead. A step that hits the limit is retried once; hitting it
again means that device is not usable: try another device (iOS: see below). When no usable device
is left, that platform's device checks are NOT RUN with the reason "timeout" (not FAIL).
A boot gets 5 minutes (emulator, bootstatus, the wait-for-device poll and the
sys.boot_completed loop each); after that the device is not usable by the same rule.
adb devices # take a serial in state "device", emulator-NNNN first
emulator -list-avds # none attached: start one in the background
emulator -avd <name> -no-snapshot-save # its serial is the new emulator-NNNN in adb devices
adb -s <serial> wait-for-device
adb -s <serial> shell getprop sys.boot_completed # repeat until it prints 1, at most 5 minutes in all
adb -s <serial> shell getprop ro.product.cpu.abilist # must contain arm64-v8aThe APK is IL2CPP ARM64. A device without arm64-v8a cannot install it: try another, else Android
device checks are NOT RUN with the ABI list. No device can be booted: same, with the command's error.
emulator -list-avds printing nothing means Android is NOT RUN, with the report line "create an
arm64 AVD in Android Studio". Do not create one automatically.
Package name: the first command prints one line, Android: <package>, confirmed after install by
pm path. ProjectSettings.asset has other Android: lines, so keep the sed range. When the
line is missing or pm path prints nothing, use the second command's package: name='...'.
sed -n '/^ applicationIdentifier:/,/^ [^ ]/p' ProjectSettings/ProjectSettings.asset | grep -E '^ Android:'
aapt2 dump badging <apk> | head -n 1adb -s <serial> uninstall <package> # emulator only, so first-launch dialogs appear
adb -s <serial> install -r <apk>
adb -s <serial> shell pm path <package>
adb -s <serial> logcat -b crash -c
adb -s <serial> shell monkey -p <package> -c android.intent.category.LAUNCHER 1
adb -s <serial> shell pidof <package> # after the wait below; empty means it died
adb -s <serial> exec-out screencap -p > qa/evidence/android/<run>-01-launch.png
adb -s <serial> logcat -d -b crash # any lines for this package are a crashAn empty PNG (the adb server restarted, or the device went offline): run adb devices, wait until
the serial is device again, and capture again. The wait is bounded, for example 6 tries 5 s apart;
if the serial never reaches device, that device is not usable (the NOT RUN rule above). Use the
serial this run already chose.
for i in 1 2 3 4 5 6; do adb devices | grep -q "^<serial>[[:space:]]*device$" && break; sleep 5; doneOn a physical device skip uninstall, and Dialogs is NOT RUN.
iOS
Prefer a simulator this run boots. A simulator that is already booted may belong to another session
and may hang. If an install, uninstall or launch on a device you did not start hits the 60 s
limit again after the retry, boot a different available iPhone yourself and use that one; never keep
working on, or shut down, the other session's device. Foldables and other odd models have no known
point scale, so prefer a plain iPhone.
xcrun simctl list devices available # the newest non-SE iPhone; boot your own
xcrun simctl bootstatus <udid> -b # boots it and waits, at most 5 minutes
open -a Simulator # when a tap tool is available: it needs the Simulator window
/usr/libexec/PlistBuddy -c 'Print :CFBundleIdentifier' "<app>/Info.plist"
xcrun simctl uninstall <udid> <bundleId>
xcrun simctl install <udid> "<app>"
xcrun simctl launch <udid> <bundleId> # prints "<bundleId>: <pid>"
xcrun simctl io <udid> screenshot qa/evidence/ios/<run>-01-launch.pngA device with several displays (foldables) fails with "Cannot choose between 2 displays". Run
xcrun simctl io <udid> enumerate, pick the main display, and pass --display=<id> before the
file: xcrun simctl io <udid> screenshot --display=1 <png>.
Both
Wait at least 10 seconds after launch before the first capture. A system tip over the game (such as
Android's "Viewing full screen / Got it") is not a permission dialog: dismiss it with a tap on its
button (Tap row, section 5), capture again and go on. Name files
<run>-NN-<what-it-shows>.png. Confirm each with file <path> (PNG, not empty), then Read it. An
install or launch error is FAIL; a step that only times out (above) is not, it is NOT RUN.
The Read tool may show a downscaled PNG, so coordinates seen in it are not device pixels. Before a tap or a touch-target measurement, read the real size and multiply what you measured by real width / displayed width. When the displayed width is unknown, work in fractions of the image and multiply them by the real size.
sips -g pixelWidth -g pixelHeight <png>Closing, after section 5
Remember which emulator or simulator this run started. Skip emu kill and simctl shutdown for any
device this run did not start.
adb -s <serial> shell am force-stop <package>
xcrun simctl terminate <udid> <bundleId>
adb -s <serial> emu kill
xcrun simctl shutdown <udid>5. Checks
Run each on each platform, and cite the PNG behind every visual result.
| Check | How | Result |
| Screen | Read the launch PNG. A single colour, the splash or the home screen: poll, capturing every 10 s until the screen changes, for up to 90 s (a heavy first menu can take over 30 s). Do not stop at the first unchanged capture | Still so, or process died, or crash lines: FAIL, and the remaining checks are NOT RUN |
| Orientation | The orientation field of design/brief.md against the PNG; judge by which way text and UI read | Mismatch FAIL. No file or field: NOT ASSESSED |
| Safe area | Text and controls clear of the notch or Dynamic Island, status bar and home indicator. Use a device that has a cutout | Control or text covered: FAIL. Android AVD without a cutout: NOT ASSESSED |
| Touch targets | Estimate each control's size in real PNG pixels (section 4, Both). Android: dp = px x 160 / density, from adb -s <serial> shell wm density, minimum 48 dp. iOS: pt = px / scale, with the scale read from the device (see below); never assume 3. Scale unreadable: the check is NOT RUN. Minimum 44 pt | Primary control clearly under the minimum (under 80% of it: 38 dp, 35 pt): FAIL. Any other shortfall: WARN |
| Thumb zone | Portrait: primary action in the lower half. Landscape: at the lower left or right | Outside: WARN |
| Tap | Android: pick the primary button's centre, scaled to real PNG pixels (section 4, Both), adb -s <serial> shell input tap <x> <y>, wait 2 s, capture, compare. No change: retry once with adb -s <serial> shell input swipe <x> <y> <x> <y> 150. iOS: simctl has no tap command (do not invent one). With a tool that can tap in the Simulator window, first run open -a Simulator, then tap there; otherwise this is NOT RUN | Still no change: FAIL. Use taps to reach the changed screen; when it cannot be reached, its visual check is NOT RUN |
| Back key | Android: adb -s <serial> shell input keyevent 4, wait 2 s, pidof, capture. iOS: n/a | Crash, or stuck (no response to the next tap, or the pid is gone): FAIL. Ignored (the screen is unchanged, the pid is the same and the next tap works), or quits from gameplay without asking: WARN |
| Background and return | Android: note pidof, input keyevent 3, wait 3 s, the monkey launch again, wait 3 s, pidof, capture. iOS: xcrun simctl launch <udid> com.apple.Preferences, wait 3 s, xcrun simctl launch <udid> <bundleId>, compare the printed pids, capture | New pid, crash or black screen: FAIL |
| Mute key | Android: adb -s <serial> shell input keyevent 164, wait 2 s, pidof, capture, send 164 again to restore. Proves only that it survives the key. The volume panel can cover part of the screen, so this PNG is not visual evidence of the screen: use a capture taken without it. iOS: no command-line control, NOT RUN | Crash or freeze: FAIL. Add "silence when muted" to Human checks |
| Dialogs | Read the first-launch PNGs for system permission or notification dialogs | Asked before the game has shown why: WARN. Blocks the game with no way past: FAIL. One you cannot dismiss: capture it, and checks behind it are NOT RUN |
iOS point scale: ios-point-scale.
Compare before and after captures by reading both PNGs. Do not grant permissions from the command line; that hides what a player sees.
6. Report
Per platform, the first match wins:
FAIL: any check isFAIL.NOT ASSESSED: build, launch or the launch PNG isNOT RUNorNOT ASSESSED. Nothing else can give this verdict.PASS WITH WARNINGS: anyWARN, or any other checkNOT RUNorNOT ASSESSED, tests included (zero tests staysNOT ASSESSEDon its own line). Each is named on theGapsline; they are gaps, not passes.PASS: every checkPASSorn/a.
Overall is the worse platform, in that order. Write qa/smoke-<run>.md, leaving out a platform
that was not requested, and do not commit it:
# Smoke <run>
Project: <name> | Unity <version> | Commit <short sha, "+ uncommitted" if dirty> | Changed: <screen or "not named">
Devices: Android <serial, model, API> | iOS <device, runtime>
| Check | Android | iOS |
|---|---|---|
| EditMode tests | PASS (42) | PASS (42) |
| PlayMode tests | NOT ASSESSED (0 tests) | NOT ASSESSED (0 tests) |
| Build | PASS | NOT RUN (no iOS Build Support) |
| Install and launch | PASS | NOT RUN |
| Screen | PASS - qa/evidence/android/<run>-01-launch.png | NOT RUN |
| <one row per other check in section 5> | | |
Verdict: Android PASS WITH WARNINGS | iOS NOT ASSESSED | Overall NOT ASSESSED
Visual: Android DONE - <PNG path>, shows <what> | iOS NOT DONE - <step and error>
Gaps: Android PlayMode tests (0 tests) | iOS PlayMode tests (0 tests)
## Findings
## Human checksVisual is per platform: DONE needs a read PNG of the changed screen, or of the launch screen when
no screen was named. One Findings entry per FAIL, in the bug-report format.
Your final message, nothing else: the Verdict and Visual lines, one line per FAIL, NOT RUN
or NOT ASSESSED check with its reason, the report path, and a last line starting Caller: with
what the caller may say. No raw logs.
What the caller may say
The work may be called done only when Visual is DONE on every requested platform and the overall
verdict is PASS or PASS WITH WARNINGS. Anything else is reported as not verified, naming the
blocker. If the user cannot wait, the caller says "looks right in the editor, not verified on a
device" and finishes the run afterwards.
Never
Edit game code, assets, scenes, tests or ProjectSettings; commit or push; close an emulator or
simulator this run did not start.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

