How do I install the Baseline skill?

Run npx skillmds@latest add meshtastic/baseline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Baseline safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Baseline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Baseline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Baseline?

meshtastic (@meshtastic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Baseline by meshtastic — Agent Skill

Name: Baseline
Author: meshtastic

Baseline

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.

meshtastic d2d014e 2.6 KB Updated Sep 17, 2026

File contents

baseline

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.

1. Bootstrap (don't skip — agent workspaces often lack these)

[ -z "$ANDROID_HOME" ] && export ANDROID_HOME="$HOME/Library/Android/sdk"

No secrets copy is needed — secrets.defaults.properties is the plugin's own fallback.

2. Decide the command from what changed

git diff --name-only HEAD && git diff --cached --name-only

Strings touched (core/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).
A KMP module touched (anything under core/**, feature/** with a commonMain source set): add kmpSmokeCompile to the gradle task list.
New top-level module: confirm its <root>/** line is in .github/workflows/pull-request.yml android: filter (else the drift guard fails the PR — #5735).

3. Run it via the gradle-runner subagent

Dispatch gradle-runner (keep the multi-thousand-line log out of context). The baseline is:

./gradlew spotlessApply spotlessCheck detekt assembleDebug test allTests

Add 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.

4. Verify the tree wasn't mutated, then clean the screenshot diff

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 --short

If gradle-runner touched files you didn't, treat its PASS as suspect and re-run the failing task inline.
The full baseline regenerates tracked screenshots as host-render noise on this machine — drop them so they don't pollute the PR:

git checkout -- docs/assets/screenshots/

5. Report

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.

---name: baselinedescription: 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.---# baselineThe 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.## 1. Bootstrap (don't skip — agent workspaces often lack these)```bash[ -z "$ANDROID_HOME" ] && export ANDROID_HOME="$HOME/Library/Android/sdk"```No secrets copy is needed — `secrets.defaults.properties` is the plugin's own fallback.## 2. Decide the command from what changed```bashgit diff --name-only HEAD && git diff --cached --name-only```- **Strings touched** (`core/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).- **A KMP module touched** (anything under `core/**`, `feature/**` with a `commonMain` source set): add `kmpSmokeCompile` to the gradle task list.- **New top-level module**: confirm its `<root>/**` line is in `.github/workflows/pull-request.yml` `android:` filter (else the drift guard fails the PR — #5735).## 3. Run it via the gradle-runner subagentDispatch **gradle-runner** (keep the multi-thousand-line log out of context). The baseline is:```./gradlew spotlessApply spotlessCheck detekt assembleDebug test allTests```Add `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.## 4. Verify the tree wasn't mutated, then clean the screenshot diffThe 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:**```bashgit status --short```- If gradle-runner touched files you didn't, treat its PASS as suspect and re-run the failing task inline.- The full baseline regenerates tracked screenshots as host-render noise on this machine — drop them so they don't pollute the PR:```bashgit checkout -- docs/assets/screenshots/```## 5. ReportOne 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.

Frequently asked questions