| name | publish-creg-testflight |
| description | Prepare, validate, upload, and verify CREG's internal-only TestFlight Beta build. Use when asked to preflight, archive, export, publish, upload, or confirm the processing status of a CREG TestFlight build. |
Publish CREG to TestFlight
Publish only CREG's Beta configuration. Preserve the repository's experimental-model and artifact-integrity gates; never substitute Release or a generic iOS publishing workflow.
Choose the operation
- For prepare, check, validate, or preflight requests, run
preflight.
- For an explicit publish or upload request, run
publish. Treat that request as authorization for the upload after every local gate passes; do not ask for another confirmation.
- Add
--dry-run when the user requests command generation without an archive or network upload.
Run from the repository root:
python3 .agents/skills/publish-creg-testflight/scripts/publish_testflight.py preflight
python3 .agents/skills/publish-creg-testflight/scripts/publish_testflight.py publish
Use raw xcodebuild only through the bundled script. The installed XcodeBuildMCP CLI has no archive, export, or App Store upload workflow.
Enforce the local gates
Let scripts/publish_testflight.py own command construction and ordering. Do not reproduce, bypass, or weaken its checks.
The script must stop before creating an archive unless:
- the complete Git worktree is clean;
- the shared
CREG scheme archives Beta;
- bundle identifier, team, automatic signing, build channel, and pinned training run match the CREG contract;
- the source build-number stamp and export-compliance declaration remain present;