Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Harness Mobile
Fastlane lane conventions for iOS + Android store delivery — beta/release/internal/production lanes, screenshot lanes, match signing with an App Store Connect API key kept out of env, scoped Play service accounts, and two-key gating on release lanes. Use when authoring a Fastfile or running fastlane to build, sign, or upload mobile binaries.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-mobileHow this skill is triggered — by the user, by Claude, or both
Slash command
/harness-mobile:addon-fastlaneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `ios beta` → build + upload to TestFlight (internal group).
Runs automated patient safety test suites for healthcare deployments, blocking on CRITICAL failures in CDSS accuracy, PHI exposure, and data integrity.
Share bugs, ideas, or general feedback.
Fastfile)ios beta → build + upload to TestFlight (internal group).ios release → build + upload to App Store, await review.android internal → build AAB + upload to Play Internal Testing.android production → build AAB + upload to Play Production track.ios screenshots → snapshot with Snapfile.android screenshots → screengrab with Screengrabfile.match with App Store Connect API key (.p8) stored in ~/.appstoreconnect/, NOT in env.--json_key; service account scoped to the one app.ios release and android production lanes refuse to run without safety.two_key=true (or a typed token). Encoded in the Fastfile template.