harbormaster
Smoke-test your mobile app from a single Claude Code prompt — before every TestFlight, App Store, or Play Store push.
Manual click-through testing is the tax you keep paying on every release. harbormaster is a Claude Code plugin that drives Maestro flows against iOS simulators and Android emulators, so the loop "I made a change → did I break anything obvious?" takes one prompt instead of fifteen minutes of taps.
Quickstart
In Claude Code:
/plugin marketplace add ConnectivityChris/harbormaster
/plugin install harbormaster@connectivity
Then, inside a mobile project (React Native, Expo, or native):
/initflow # one-time: scaffolds .maestro/ with starter flows
/authorflow login # add a flow with a guided interview + screen capture
That's it. The skill preflights your env, boots a sim, installs your build, runs the flows, and reports pass/fail with screenshots, video, and JUnit XML.
What you get
- One-prompt regression runs. "Smoke test the build" → preflight → boot sim → install → run flows → diagnosis. No bespoke CI, no scripted glue code on your side.
- Guided flow authoring. Slash commands walk you through composing flows with screen captures, accessibility-tree inspection, and selector picking — so flows actually run hands-off the first time.
- iOS + Android, dev build or Expo Go. Per-platform device picker, dev-build install, or Expo Go deep-link. Defaults to dev build for hands-off reliability.
- Credentials never persisted. Reads from your shell env or prompts per-run. No
.env writes, no Keychain integration, no surprises.
- Token-aware failure diagnosis. When a flow fails, the skill reads logs first, then the live UI hierarchy, and only loads screenshots if the failure is visual — keeping context windows lean.
The four commands
| Command | When to use |
|---|
/initflow | First time on a project — scaffolds .maestro/ with starter flows tuned to your project |
/buildsuite | Build a core suite of flows in one session via a guided tour + per-flow checkpoints |
/authorflow [flow-name] | Add a single flow — guided interview, screen capture, selector picking, run |
/stabiliseflow <flow> [N] | Harden a flow before relying on it as a release gate — runs N times, reports flake rate |
The skill also triggers on natural-language prompts (e.g. "smoke test the iOS build before I push") — slash commands are the explicit entry points.
Why harbormaster vs the alternatives
| harbormaster | Bare Maestro CLI | Detox | Manual QA |
|---|
| Authoring help | Guided, AI-assisted | DIY YAML | JS test code | n/a |
| Sim/emulator orchestration | Built-in | DIY shell | Built-in | n/a |
| Failure diagnosis | Tiered, token-aware | Raw logs | Stack traces | Memory |
| Setup time | One install | Hours | Days | Zero |
| Best for | Pre-release smoke | Custom CI | Deep RN-internal asserts | One-off checks |
Use Detox or unit tests where you need them. harbormaster owns the "is this build OK to ship?" loop.
Prerequisites
Install
# Inside Claude Code (recommended — pin to a release tag)
/plugin marketplace add ConnectivityChris/[email protected]
/plugin install harbormaster@connectivity
Drop the @v0.5.1 to track HEAD instead. Pinning is recommended for stable workflows; HEAD is fine if you want unreleased changes.
Project setup
Run /initflow from inside your mobile project. It discovers your bundleId / package, detects auth, and scaffolds .maestro/ with starter flows, an onboarding README, and a config.json of skill defaults.
