菜单
Use for EAS builds and App Store submission - production build, eas submit, attaching subscriptions to the version, submitting for review (Stage 5 of SUBMISSION.md)
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | build-and-submit |
| description | Use for EAS builds and App Store submission - production build, eas submit, attaching subscriptions to the version, submitting for review (Stage 5 of SUBMISSION.md) |
npm run doctor passes (run it now; if it fails, route to
submission-doctor and stop).eas whoami succeeds. If not, ask the user to run ! eas login.app.config.js extra.eas.projectId is missing, run eas init and
commit the change (follow the dev lifecycle in CLAUDE.md - issue, branch,
PR).eas build --platform ios --profile production --non-interactive.
First-ever build needs Apple credentials setup, which is interactive:
if the command fails asking for credentials, ask the user to run
! eas build --platform ios --profile production themselves once, then
resume here.eas build:list --platform ios --limit 1.
On failure, fetch the log URL it prints, read the failing phase, report
the root cause, and fix before retrying.eas submit --platform ios --latest. This uploads the build to ASC.Use when creating a new .NET CLI/console project from the agent-harness template ("new cli tool", "new console app", "new dotnet project"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new .NET ETL/API service from the agent-harness template ("new api", "new etl service", "new backend service"). Scaffolds, stamps provenance, and verifies guardrails.
Use when creating a new Expo/React Native app from the agent-harness template ("new expo app", "new mobile app", "scaffold an app with payments"). Scaffolds, stamps provenance, and verifies guardrails.
Use at session start when config-doctor reports the project is not build/deploy-ready, or when the user asks to set up the project - interviews the user, gets EAS logged in / project linked / iOS credentials provisioned and a real bundle id, offers optional payments/auth/API config, and records decisions so the session-start nudge goes quiet
Use when asked to report harness feedback, promote captured guardrail failures into issues, or check "anything worth turning into a rule?". Clusters unreported feedback events and raises digest issues on the agent-harness repo.
Use after a PR merges, or on request, to capture human review comments from a PR into the harness feedback store ("capture the review comments", "harvest PR feedback"). Routed from the merge step.