Back to Details

ship

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GStack Ship

GStack Ship

Select one release stage, preserve human and automated gates, and make every external mutation explicit.
选择一个发布阶段，保留人工与自动化闸门，让所有外部变更操作透明化。

Required execution header

必需执行头

Before any substantive output, print these exact labels in this exact order. Resolve the specialist refinement first; do not put prose above the header.
text
Target: <concrete repository, product, URL, device, PR, or artifact>
Mode: <selected top-level mode>
Depth: <readiness, standard, or deep>
Mutation: <report-only or exact authorized mutation boundary>
Active modules: <comma-separated internal specialist modules>
Skipped modules: <comma-separated non-active mandatory modules with compact reasons>
Web context: <none, optional, local-browser, or production>
在输出任何实质性内容之前，按以下精确顺序打印这些标签。先完成专业模块的细化；不要在执行头上方添加任何说明文字。
text
Target: <具体仓库、产品、URL、设备、PR或工件>
Mode: <选定的顶级模式>
Depth: <就绪、标准或深度>
Mutation: <仅报告或明确授权的变更边界>
Active modules: <逗号分隔的内部专业模块>
Skipped modules: <逗号分隔的非活跃必填模块及简要原因>
Web context: <无、可选、本地浏览器或生产环境>

Dispatch protocol

调度协议

  1. Infer the mode from product stage, surface, requested artifact, mutation authorization, evidence needs, and deployment state. Do not route by keyword alone.
  2. Refine the public mode to the smallest applicable internal specialist set, then print the required execution header before any substantive output.
  3. Read each active module in full from the path shown in the mode/alias tables. Its specialist body, behavioral contract, STOP gates, and appended upstream judgment ports are binding. Read a lazy specialist phase in full only when the workflow reaches its package-local reference.
  4. Read 
    references/EXECUTION-PROFILES.md
    , 
    references/SHARED-JUDGMENT.md
    , and 
    references/AUTHORITY-POLICY.md
    for every invocation. Read 
    references/QUESTION-FORMAT.md
    before the first question to the user; it owns the decision-brief format, the structured-payload caps, and the prose fallback when no question tool is available. Infer Depth from structured operating conditions, then obey its mandatory modules, legal skips, artifacts, and claim limits. Read 
    references/RUNTIME.md
    before capability-dependent work and 
    references/WEB-CONTEXT.md
    before public-web work. When the target is a repository, read 
    references/CODE-INTELLIGENCE.md
    once before substantive specialist work and follow its one-time indexing offer. Read 
    references/THIRD-PARTY-ACTIONS.md
    before directing the user to act on a third-party website (API key registration, vendor accounts, dashboards).
  5. If an old asset path is unavailable, use 
    references/ASSETS.md
    . If legacy prose invokes another retired skill, resolve it through 
    references/COMPATIBILITY.md
    and stay inside these five dispatchers.
  6. Preserve report-only versus mutation boundaries. Missing mutation authorization fails closed: do not edit merely because a specialist can fix. Commits, pushes, PRs, merges, deploys, messages, and other external mutations still require affirmative authority from the user.
  7. Match the user's language. Keep code identifiers, commands, and source quotations original when translation would reduce accuracy.
  8. At exit, report completed artifacts, evidence, unresolved decisions, skipped modules with reasons, and any blocked gate.
  9. Before push, PR creation/update, merge, deploy, rollback, release publication, or external notification, read 
    references/EXTERNAL-EFFECTS.md
    and execute the action through its durable state wrapper.
  10. When the release target is an Apple platform app (an 
    .xcodeproj
    , 
    .xcworkspace
    , or app-product Swift package is present), read 
    references/APPLE-RELEASE.md
    FIRST — before any specialist preflight or repository gate — and follow its App Store journey end to end. An App Store or TestFlight ask is store distribution, not repository landing: the specialist branch/PR ceremony does not gate it, and a clean tree on the base branch is a valid state to archive and upload from.
  1. 根据产品阶段、界面、请求的工件、变更授权、证据需求和部署状态推断模式。不要仅通过关键字进行路由。
  2. 将公开模式细化为最小适用的内部专业模块集合，然后在输出任何实质性内容之前打印必需执行头。
  3. 从模式/别名表中所示路径完整读取每个活跃模块。其专业主体、行为契约、STOP闸门以及附加的上游判断端口具有约束力。仅当工作流到达其包本地引用时，才完整读取延迟加载的专业阶段。
  4. 每次调用时都要读取
    references/EXECUTION-PROFILES.md
    、
    references/SHARED-JUDGMENT.md
    和
    references/AUTHORITY-POLICY.md
    。在向用户提出第一个问题之前，读取
    references/QUESTION-FORMAT.md
    ；它定义了决策摘要格式、结构化负载上限，以及在没有可用问题工具时的文本回退方案。根据结构化操作条件推断Depth，然后遵守其必填模块、合法跳过项、工件和声明限制。在进行依赖能力的工作之前读取
    references/RUNTIME.md
    ，在进行公共网络工作之前读取
    references/WEB-CONTEXT.md
    。当目标是仓库时，在进行实质性专业工作之前读取一次
    references/CODE-INTELLIGENCE.md
    并遵循其一次性索引提议。在指导用户在第三方网站执行操作（API密钥注册、供应商账户、仪表板）之前，读取
    references/THIRD-PARTY-ACTIONS.md
    。
  5. 如果旧资产路径不可用，使用
    references/ASSETS.md
    。如果旧版文本调用了另一个已停用的技能，通过
    references/COMPATIBILITY.md
    解决，并保持在这五个调度器范围内。
  6. 保留仅报告与变更操作的边界。缺少变更授权则默认拒绝：不要仅仅因为专业模块可以修复就进行编辑。提交、推送、PR、合并、部署、消息和其他外部变更操作仍需要用户明确授权。
  7. 匹配用户使用的语言。当翻译会降低准确性时，保留代码标识符、命令和源代码引用的原始形式。
  8. 在退出时，报告已完成的工件、证据、未解决的决策、带有原因的跳过模块以及任何被阻塞的闸门。
  9. 在推送、创建/更新PR、合并、部署、回滚、发布版本或发送外部通知之前，读取
    references/EXTERNAL-EFFECTS.md
    并通过其持久状态包装器执行操作。
  10. 当发布目标是Apple平台应用（存在
    .xcodeproj
    、
    .xcworkspace
    或应用产品Swift包）时，首先读取
    references/APPLE-RELEASE.md
    ——在任何专业预检或仓库闸门之前——并全程遵循其App Store发布流程。App Store或TestFlight相关请求属于商店分发，而非仓库落地：专业分支/PR流程不会对其进行管控，基础分支上的干净代码树是可归档并上传的有效状态。

Top-level modes

顶级模式

ModeTargetInfer whenCandidate internal specialists
Prepare
A working branch or release artifactThe work needs checks, review, release metadata, documentation, commit, push, PR creation, or queue status.
references/legacy/ship.md
, 
references/legacy/landing-report.md
, 
references/legacy/document-release.md
Land
An approved open PRThe requested next irreversible stage is merge/landing.
references/legacy/land-and-deploy.md
Deploy
A landed change or deploy configurationThe change is ready for deployment or deployment must first be configured.
references/legacy/setup-deploy.md
, 
references/legacy/land-and-deploy.md
Monitor
A production deploymentThe deploy needs thresholded continuous canary monitoring.
references/legacy/canary.md
Resume
An interrupted release operationPersisted release state must be restored and authoritative external state reconciled before continuing.
references/legacy/context-restore.md
, 
references/legacy/land-and-deploy.md
模式目标推断时机候选内部专业模块
Prepare
工作分支或发布工件需要进行检查、审核、发布元数据、文档、提交、推送、创建PR或查看队列状态时。
references/legacy/ship.md
, 
references/legacy/landing-report.md
, 
references/legacy/document-release.md
Land
已获批的公开PR请求的下一个不可逆阶段是合并/落地时。
references/legacy/land-and-deploy.md
Deploy
已落地的变更或部署配置变更已准备好进行部署，或需要先配置部署时。
references/legacy/setup-deploy.md
, 
references/legacy/land-and-deploy.md
Monitor
生产环境部署需要对部署进行阈值化持续金丝雀监控时。
references/legacy/canary.md
Resume
中断的发布操作需要恢复持久化发布状态并在继续之前协调权威外部状态时。
references/legacy/context-restore.md
, 
references/legacy/land-and-deploy.md

Hard rules

硬性规则

  • Never force push or bypass failing tests.
  • A requested human review is a hard merge gate unless the user gives the dedicated explicit override.
  • Breaking-change analysis overrides line-count bump heuristics.
  • 永远不要强制推送或绕过失败的测试。
  • 请求的人工审核是硬性合并闸门，除非用户给出专门的明确覆盖权限。
  • 破坏性变更分析优先于代码行数增量启发式规则。

Internal specialist routing aliases

内部专业模块路由别名

Every specialist below is an internal implementation detail, including mandatory inputs. The legacy alias refines a top-level mode; it never adds a public skill or top-level mode.
Legacy invocationLegacy aliasPublic modeRoleModule
/ship
ship
Prepare
mandatory
references/legacy/ship.md
/land-and-deploy
land
Land
mandatory
references/legacy/land-and-deploy.md
/landing-report
queue
Prepare
mandatory
references/legacy/landing-report.md
/document-release
docs
Prepare
mandatory
references/legacy/document-release.md
/setup-deploy
setup
Deploy
mandatory
references/legacy/setup-deploy.md
/document-generate
docs-generate
Prepare
supporting
references/legacy/document-generate.md
/gstack-upgrade
upgrade
Prepare
supporting
references/legacy/gstack-upgrade.md
/ios-clean
ios-clean
Prepare
supporting
references/legacy/ios-clean.md
/ios-sync
ios-sync
Prepare
supporting
references/legacy/ios-sync.md
以下所有专业模块均为内部实现细节，包括必填输入。旧版别名用于细化顶级模式；它绝不会添加公开技能或顶级模式。
旧版调用旧版别名公开模式角色模块
/ship
ship
Prepare
必填
references/legacy/ship.md
/land-and-deploy
land
Land
必填
references/legacy/land-and-deploy.md
/landing-report
queue
Prepare
必填
references/legacy/landing-report.md
/document-release
docs
Prepare
必填
references/legacy/document-release.md
/setup-deploy
setup
Deploy
必填
references/legacy/setup-deploy.md
/document-generate
docs-generate
Prepare
支持
references/legacy/document-generate.md
/gstack-upgrade
upgrade
Prepare
支持
references/legacy/gstack-upgrade.md
/ios-clean
ios-clean
Prepare
支持
references/legacy/ios-clean.md
/ios-sync
ios-sync
Prepare
支持
references/legacy/ios-sync.md

Completeness invariant

完整性不变量

Do not work from this dispatcher summary when a module is active. Read the referenced module completely, including its provenance marker, specialist workflow, lazy-phase directives, behavioral contract, and bug-fix overlays. The pinned 1.x shared onboarding wrapper is provenance-only and never runs during canonical execution.
当模块处于活跃状态时，不要仅依据此调度器摘要开展工作。完整读取引用的模块，包括其来源标记、专业工作流、延迟阶段指令、行为契约和错误修复覆盖层。固定的1.x共享入门包装器仅用于标记来源，在标准执行过程中绝不会运行。