adb-mcp: Skill for Claude Code

Cutting an adb-mcp release

Everything runs off one tag push. .github/workflows/release.yml triggers only on v* — there is no push/PR CI — so the tag is simultaneously the build, the test run, the GitHub Release, and the MCP registry publish. A bad tag is therefore public before you find out.

The rule that follows from that: replicate the gate locally before tagging. Re-tagging is the only fix, and the registry has already seen the old version.

Order of operations

1. Review what landed since the last tag.
2. Verify the new tools live (see below — this is not optional here).
3. Fix what the review found. Do not tag around a known bug in unreleased code.
4. Bump the four version files + write the CHANGELOG section.
5. make docs to sync every derived count.
6. Run the gate locally.
7. Tag, push, watch, confirm.
8. Pin the Claude plugin to the release (make plugin-pin TAG=vX.Y.Z), commit, push.

1. Review

git fetch && git status -sb  # local main can be behind: features land from other sessions and machines
git merge --ff-only origin/main  # alone, never piped; then review what you will tag
git log --oneline "$(git describe --tags --abbrev=0)"..HEAD
git status --short          # uncommitted feature work is common here
git diff

Working-tree changes matter as much as commits: features often sit uncommitted with their docs already written. Read docs/BACKLOG.md — entries are updated to [x] with a "Verified…" note when something ships, and that note is a claim you are about to put your name on.

2. Verify live, don't reason from the diff

A passing go test says the parser works. It does not say the tool works. Drive the freshly built binary over real stdio JSON-RPC:

go build -o "$SCRATCH/adb-mcp" ./cmd/adb-mcp
python3 .claude/skills/release/mcp_drive.py "$SCRATCH/adb-mcp" \
  'session_set_defaults|{"project_dir":"/path/to/project"}' \
  'get_coverage_report|{}'

mcp_drive.py flushes each line as it prints, times out a step after 120s by default (--timeout N, or 'name|{json}|SECONDS' for one slow step such as a Gradle build), names the step that hung and ends with its summary. With an emulator already up, boot_emulator {"avd": "<name>"} alone must return its serial; that default call is the one that broke in v0.24.4.