發布工程

來源狀態

可用來源

原始名稱: shipping-and-launch

原始作者: Addy Osmani

這是第三方 Community Skill；2lus 收錄不代表已完整安全審計或保證安全。

資源類型

Skill

與類似 Skill 有什麼不同？

• CI/CD 持續交付

  Release Engineering 安排一次版本發布、觀察與回復；CI/CD 建立可重複執行的交付 pipeline。

來源描述的能力

這些是來源描述的可能操作，不代表 2lus 已授予權限或已測試。

尚未列出能力，請審查原始來源。

這個 Skill 是什麼？

把版本交付、觀察與回復責任串成可交接的發布計畫。

可以做什麼？何時適合使用？

• 準備功能首次上線
• 規劃 feature flag rollout
• 安排 migration 與 rollback

如何使用

1. 確認版本、artifact 及既有驗證證據
2. 整理 changelog、migration 與發布責任人
3. 設計分段觀察及中止條件，等待發布核准

使用前你需要準備

• 目標工作流程與現況
• 可執行操作的授權界線

你可以替換：

[target branch]、[workflow]

環境與相依需求

• 需要發布範圍、pipeline 結果與操作限制；保留來源參考。

使用範例與 Prompt

以下是 2lus 撰寫的示範需求；請替換為你有權處理的檔案與專案，不代表已執行或保證結果。

入門

替附件版本差異整理 release notes，列出版本、artifact 與待完成檢查，不建立 tag。

實務

為匯出功能設計內部啟用到分段 rollout 的順序、監控門檻與關閉 flag 的條件。

進階

安排含資料 migration 的 release handoff，區分 code rollback、資料復原與 forward fix，列出核准者及部署後驗證證據。

實用提醒

• 把部署與功能啟用分開，為 flag 設定 owner 與清理期限。

限制與注意事項

• 清單完整不代表 release 已成功；有些資料變更無法直接回復。

安全注意事項

• 發布、打 tag、推送及 migration 必須明確授權；不可把缺少測試寫成通過。

使用與設定

此條目不提供已確認的通用安裝指令；請依官方文件與 Agent 版本操作。

支援平台

未確認特定 Agent 相容性

來源與授權

來源查核日期（非安全認證）: 2026-09-29

MIT

相關 Skills

• CI/CD 持續交付
• Git 工作流程
• 正式環境就緒審查

Source status

Active source

Original name: shipping-and-launch

Original author: Addy Osmani

This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.

Resource type

Skill

How is this different from similar skills?

• CI/CD

  Release Engineering coordinates one release, observation and recovery; CI/CD builds the reusable delivery pipeline.

Documented capabilities

These are operations described upstream, not permissions granted or tested by 2lus.

Capabilities not declared here; review the original source.

What is this skill?

Connect delivery, observation and recovery responsibilities for one release.

Use cases and when to use it

• Prepare a first launch
• Plan feature-flag rollout
• Coordinate migration and rollback

How to use it

1. Identify version, artifacts and existing evidence
2. Prepare notes, migrations and owners
3. Define observation and stop conditions before approval

What you need

• Target workflow and current state
• Authorization boundaries

You can replace:

[target branch], [workflow]

Environment and dependencies

• Provide release scope, pipeline evidence and operational constraints; retain references.

Usage and prompt examples

These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.

Beginner

Draft release notes from this version diff with artifact and pending-check lists; do not create tags.

Practical

Plan an export-feature rollout from internal users to cohorts with monitoring thresholds and flag-disable conditions.

Advanced

Prepare a migration release handoff distinguishing code rollback, data restoration and forward fixes, with approvers and post-deployment evidence.

Tips

• Separate deployment from enablement; assign flag ownership and cleanup dates.

Limitations

• A completed checklist does not prove release success; data changes may be irreversible.

Security notes

• Publishing, tagging, pushing and migrations require authorization; missing tests are not passes.

Usage and setup

No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.

Supported agents

Specific agent compatibility unknown

Sources and license

Source check date (not a safety certification): 2026-09-29

MIT

Related skills

• CI/CD
• Git Workflow
• Production Readiness Review