← ClaudeAtlas

kappmaker-ios-cilisted

Build and ship a KAppMaker iOS app from GitHub Actions, so no Mac is needed locally — TestFlight and App Store releases, signing, metadata and screenshots included. Use when the user has no Mac, when an iOS build fails because Xcode is missing (Linux boxes, CI, a Windows machine), or when they ask to publish/ship/release iOS, send a build to TestFlight, or set up iOS CI.
KAppMaker/KAppMaker-CLI · ★ 3 · DevOps & Infrastructure · score 64
Install: claude install-skill KAppMaker/KAppMaker-CLI
# KAppMaker — iOS from CI (no Mac needed) Xcode only runs on macOS, so a Linux box cannot compile an iOS app. Everything *around* the compile — App Store Connect records, products, metadata, ASO — the CLI already does over the API from anywhere. This skill closes the one real gap by renting a Mac for the ~20 minutes the compile takes: a GitHub-hosted macOS runner does the build, signs it, and uploads it. **The runner is the Mac.** The user never installs Xcode, never handles a certificate, never owns Apple hardware. ## Before running any command 1. **Prerequisites** — `kappmaker --version` (install: `npm i -g kappmaker`), plus `gh` logged in (`gh auth login`) since everything runs through the user's own GitHub account. 2. **App Store Connect API key in config** — `ascKeyId`, `ascIssuerId`, `ascPrivateKeyPath`, exactly as for `kappmaker create-appstore-app`. 3. The project must be a GitHub repo, and the ASC app record must exist (**kappmaker-asc**). ### ios-ci init — one-time setup **Syntax**: `kappmaker ios-ci init [--repo <owner/name>] [--certs-repo <owner/name>] [--match-password <value>] [--mobile-dir <path>] [--dry-run]` Run it from the project root. It: 1. reads the bundle ID from the Xcode project and the repo from the git remote, 2. checks `.github/workflows/publish_ios_appstore.yml` by capability, not by a version marker — **the boilerplate already ships this workflow**, so an up-to-date project is left alone. Only a project missing part of t