agentleFS
gronxbgronxb/codex-relay/.agents/skills/hot-updater-qa-ship/SKILL.md

hot-updater-qa-ship

Skill733 starsChanged 2 months agoApache-2.0View on GitHub

Deploy the current Modex iOS app version with Hot Updater for QA-only delivery. Use when the user invokes $hot-updater-qa-ship or asks to ship the current iOS OTA to one target cohort only, with rollout 0.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user for only the target cohort when it is not already provided.

    line 14
  2. Distinctive:

    Read the current native app versions:

    line 33
  3. Very specific:

    Wait for the deploy command to finish.

    line 50
  4. Very specific:

    Use --json as well when you want machine-readable confirmation from the update command:

    line 62
  5. Distinctive:

    Verify the Bundle state:

    line 69
  6. Distinctive:

    If the app version command fails, report the error and do not deploy.

    line 82
  7. Very specific:

    If deploy fails, stop immediately.

    line 83
  8. Very specific:

    If the deployment summary does not contain a Bundle ID, run pnpm hot-updater bundle list -p ios --target-app-version <ios-app-version> …

    line 84
  9. Distinctive:

    If the Bundle ID is unavailable, stop rather than guessing which Bundle was created.

    line 87
  10. Very specific:

    If bundle update fails, report the Bundle ID and update error.

    line 89
  11. Distinctive:

    If verification fails, report the mismatch and Bundle ID.

    line 90
  12. Distinctive:

    Do not hardcode an app version.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hot Updater QA Ship

Deploy the current iOS OTA bundle to the configured production channel with rollout 0, then attach exactly one target cohort to the newly created Bundle.

Required Input

Ask the user for only the target cohort when it is not already provided. Do not ask for platform, channel, rollout, or app version.

Target cohort rules:

  • Trim surrounding whitespace.
  • Reject empty values.
  • Accept only one cohort value. If the user provides multiple values, ask for a single cohort.
  • Pass the cohort to Hot Updater exactly as the validated trimmed string.

Workflow

  1. Work from the mobile app directory:
cd apps/mobile
  1. Read the current native app versions:
pnpm hot-updater app-version --json
  1. Extract the current ios app version. Treat numeric JSON values as strings when passing them to the CLI. If --json is not supported, run pnpm hot-updater app-version and parse the iOS version from the human-readable output.
  2. Deploy the current iOS app version with rollout 0:
pnpm hot-updater deploy -p ios -t <ios-app-version> -r 0
  1. Wait for the deploy command to finish. Success requires build complete, storage upload complete, database update complete, and Deployment Successful (<bundle-id>).
  2. Extract <bundle-id> from the ID row in the deployment summary.
  3. Attach the target cohort to that exact Bundle without prompting:
pnpm hot-updater bundle update <bundle-id> --target-cohorts "<target-cohort>" -y

Use --json as well when you want machine-readable confirmation from the update command:

pnpm hot-updater bundle update <bundle-id> --target-cohorts "<target-cohort>" -y --json
  1. Verify the Bundle state:
pnpm hot-updater bundle show <bundle-id> --json

Confirm the resulting Bundle has id equal to the deployed Bundle ID, platform equal to ios, target_app_version equal to the current iOS app version, rollout_cohort_count equal to 0, and target_cohorts equal to an array containing exactly the requested target cohort.

Failure Handling

  • If the app version command fails, report the error and do not deploy.
  • If deploy fails, stop immediately. Do not run bundle update.
  • If the deployment summary does not contain a Bundle ID, run pnpm hot-updater bundle list -p ios --target-app-version <ios-app-version> --limit 5 --json and identify the newly created Bundle before updating it.
  • If the Bundle ID is unavailable, stop rather than guessing which Bundle was created.
  • If bundle update fails, report the Bundle ID and update error.
  • If verification fails, report the mismatch and Bundle ID.

Notes

  • This skill always targets iOS.
  • This skill always uses rollout 0.
  • This skill uses the Hot Updater default channel, currently production, unless the repo configuration or CLI default changes.
  • Do not hardcode an app version. Always read the current iOS version at deploy time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.