正式環境就緒審查

來源狀態

可用來源

原始名稱: production-readiness

原始作者: magnus919

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

資源類型

Skill

與類似 Skill 有什麼不同？

• 程式碼變更審查

  Production Readiness Review 彙整跨領域上線證據與責任人；Code Review 檢視變更本身，不等同整體上線核准。

來源描述的能力

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

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

這個 Skill 是什麼？

依風險檢查上線前證據，而非僅以測試成功判定可上線。

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

• 審查新服務上線
• 檢查高風險權限變更
• 追蹤 migration 發布缺口

如何使用

1. 說明變更範圍及最高風險面向
2. 逐項連結 ownership、安全、資料、監控與回復證據
3. 列出缺口、owner、期限與 go/no-go/defer 建議

使用前你需要準備

• 預期與實際行為
• 去識別化錯誤紀錄和相關程式

你可以替換：

[test framework]、[failure]

環境與相依需求

• 提供指定 release 的審查、測試、維運與回復紀錄；保留來源模板。

使用範例與 Prompt

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

入門

檢視這份內部文件發布計畫，列出 owner、影響與回復證據，不擴大成完整系統稽核。

實務

整理新 API 上線的 functional、error handling、logging、monitoring 與 security 證據表，標記缺口及負責人。

進階

審查涉及權限與 migration 的 production release，檢查效能、configuration、secrets、rollback 和 runbook；提出 no-go 或 defer 條件，不能自行核准例外。

實用提醒

• 功能、效能、configuration、secrets 與文件都應對應具名證據，不以總分掩蓋風險。

限制與注意事項

• 不是重新執行 QA、安全掃描或部署；人工豁免不得由 Agent 自行授予。

安全注意事項

• 報告遮蔽 secrets 與個資；例外上線需要具名人工核准。

使用與設定

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

支援平台

未確認特定 Agent 相容性

來源與授權

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

MIT

相關 Skills

• 程式碼變更審查
• 發布工程
• 可觀測性

Source status

Active source

Original name: production-readiness

Original author: magnus919

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?

• Code Review

  Production Readiness Review assembles cross-domain launch evidence and owners; Code Review examines changes rather than granting launch approval.

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?

Review risk-scaled evidence instead of treating green tests as launch approval.

Use cases and when to use it

• Review a service launch
• Assess authorization changes
• Track migration release gaps

How to use it

1. Declare scope and the highest-risk dimension
2. Link ownership, security, data, monitoring and recovery evidence
3. Assign gaps, owners and dates with a go/no-go/defer recommendation

What you need

• Expected and actual behavior
• Redacted errors and relevant code

You can replace:

[test framework], [failure]

Environment and dependencies

• Supply release-specific reviews, tests and operational records; retain source templates.

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

Review this internal documentation release for ownership, impact and recovery evidence without broadening into a system audit.

Practical

Build a new API launch evidence table covering functionality, errors, logging, monitoring and security with gap owners.

Advanced

Review an authorization and migration release for performance, configuration, secrets, rollback and runbooks; recommend no-go/defer conditions without approving exceptions.

Tips

• Connect functionality, performance, configuration, secrets and documentation to named evidence.

Limitations

• This does not execute QA, security scans or deployment; agents cannot grant human exceptions.

Security notes

• Redact secrets and personal data; exceptional launch approval requires a named human.

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

• Code Review
• Release Engineering
• Observability