git:20260407.3da80bb to git:20260420.1cc7572

13 added, 1 removed. Audit A to A.

---

name: deploy

description: Build the current project and upload the app binary to DeployGate

+ allowed-tools: mcp__deploygate__get_user_info mcp__deploygate__upload_app Bash(./gradlew:*) Bash(fastlane:*) Bash(xcodebuild:*) Bash(git rev-parse:*) Bash(which:*) Read Glob

---

# Build and upload app to DeployGate

- Build the current project and upload the binary to DeployGate.

+ Build the current project and upload the binary to DeployGate. This is the **fast-path** skill — a quick build + upload for a project that is already set up. For first-time setup, iOS code signing issues, UDID registration, distribution page creation, or notification configuration, escalate to the `setup` skill instead.

+ ## When to escalate to the `setup` skill

+ Stop this skill and suggest the user invoke `setup` if any of these apply:

+ - The user has never uploaded to DeployGate before (no API token configured)

+ - iOS build fails with a code signing / provisioning profile error

+ - A tester reports they can't install the app (UDID registration needed)

+ - The user needs to create or configure a distribution page

+ - The user wants to configure notifications

+ The `setup` skill owns the full onboarding flow and its detailed references cover these paths.

## Steps

1. **Detect project type** by checking for build files:

- `build.gradle` / `build.gradle.kts` → Android

- `*.xcodeproj` / `*.xcworkspace` → iOS

- If both exist, ask the user which platform to build

2. **Get owner name** using the `get_user_info` MCP tool

3. **Build the app**:

- Android: `./gradlew assembleDebug` → `app/build/outputs/apk/debug/app-debug.apk`

- iOS: guide the user to build with `fastlane gym` or Xcode Archive, then provide the IPA path

- Do NOT use APKs from Android Studio's Instant Run / Apply Changes

4. **Collect Git info** for the upload message:

```bash

git rev-parse --short HEAD # commit hash

git rev-parse --abbrev-ref HEAD # branch name

```

Format: `"{branch} ({hash})"` — e.g. `"feature/login (abc1234)"`

5. **Upload** using the `upload_app` MCP tool:

- `owner_name`: from step 2

- `file_path`: path to the built binary

- `message`: Git info from step 4

- If the user specifies a distribution page, include `distribution_key` or `distribution_name`

6. **Show results**: display the upload response including the app URL and revision number

## Options

The user can specify:

- Distribution page name: `/deploy to "Beta"` → sets `distribution_name: "Beta"`

- Distribution page key: `/deploy to key:abc123` → sets `distribution_key: "abc123"`

- Custom message: `/deploy with message "hotfix build"` → overrides auto-generated message