melvynx/aiblueprint

appstore-connect

Drive App Store Connect through the asc CLI for apps, builds, TestFlight, reviews, sales, metadata, IAP, signing, and submissions.

ソースを見る
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Inspect first, mutate second. Discover flags from the CLI; do not guess them.

bash
asc auth status
asc auth status --validate
asc doctor
asc --help
asc <area> --help
asc docs list

Use --profile <name> when more than one account exists. A new account with no stored key: run find-asc-credentials, then asc auth login. Never print or commit .p8 keys, key ids, issuer ids, or downloaded financial reports with PII.

Resolve the numeric app id once: asc apps list --output json. Use --output json when parsing ids.

GoalArea
Apps / statusasc apps, asc status --app <id>
Buildsasc builds
TestFlightasc testflight, asc publish testflight
Versions / releaseasc versions, asc release
Metadata / screenshotsasc metadata, asc localizations, asc screenshots
Pricing / IAPasc pricing, asc iap, asc subscriptions
Submitasc validate, asc review, asc submit, asc publish
Reviews / salesasc reviews, asc analytics, asc insights, asc finance
Signing / teamasc signing, asc certificates, asc profiles, asc users

Confirm before any externally visible or hard-to-reverse mutation (submit, publish ... --submit, pricing, IAP, user changes, certificate or profile deletion). State the app id, version, and exact change. Run asc validate before submitting. Prefer --dry-run when it exists.

This skill owns the store side only. For an endpoint asc does not expose:

bash
node "$SKILL_DIR/scripts/asc-api.mjs" GET "/v1/apps?filter[bundleId]=com.example.app"

Credentials from env (ASC_KEY_ID, ASC_ISSUER_ID, ASC_P8_PATH); never hardcode them.

同じリポジトリから

関連する Skills

すべての Skills