Run the mandatory pre-push baseline verification for Meshtastic-Android — bootstrap, then spotlessApply/spotlessCheck/detekt/assembleDebug/test/allTests (plus kmpSmokeCompile and sort-strings when relevant) via the gradle-runner subagent, restore the host-render screenshot diff, and report a single pass/fail. Use before every push. This is the check CI fails on when skipped.
79
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
The repo's verify-before-push gate, codified. CLAUDE.md/AGENTS.md mandate this before every push and CI has failed repeatedly when it was skipped. Run it, don't paraphrase it.
[ -z "$ANDROID_HOME" ] && export ANDROID_HOME="$HOME/Library/Android/sdk"
[ -f local.properties ] || cp secrets.defaults.properties local.propertiesgit diff --name-only HEAD && git diff --cached --name-onlycore/resources/.../values/strings.xml): prepend python3 scripts/sort-strings.py (the PostToolUse hook usually already did this; running it again is a no-op if so).core/**, feature/** with a commonMain source set): add kmpSmokeCompile to the gradle task list.<root>/** line is in .github/workflows/pull-request.yml android: filter (else the drift guard fails the PR — #5735).Dispatch gradle-runner (keep the multi-thousand-line log out of context). The baseline is:
./gradlew spotlessApply spotlessCheck detekt assembleDebug test allTestsAdd kmpSmokeCompile to that line if step 2 flagged a KMP module. Both test and allTests are required — allTests covers KMP modules (where bare test silently skips), test covers pure-Android/JVM modules.
The gradle-runner subagent has Bash and has been observed reverting/editing files to force a green build. After it returns, confirm the only changes are yours:
git status --shortgit checkout -- docs/assets/screenshots/One line: BASELINE PASS (+ any inline re-runs you did) or BASELINE FAIL with the failing task/test names from gradle-runner. Do not push on FAIL.
92e3300
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.