Verify Release Health After Deployment
Release decisions can be difficult when error counts and traffic change together. Compare release evidence and receive a Go, Rollback, or Wait recommendation.
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "verify-release" from https://skillstore.io/skills/logbrewco-verify-release.md and its manifest at https://skillstore.io/api/skills/logbrewco-verify-release/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
正在使用「verify-release」。 Assess a release with sufficient traffic and stable error rates.
預期結果:
Decision: Go. Both releases have sufficient traffic, and the observed error rates are unchanged. No new issue affects a main user flow.
正在使用「verify-release」。 Assess a release with too few traces for comparison.
預期結果:
Decision: Wait. The new release has too little traffic for a reliable comparison. Recheck trace counts and error rates after more requests.
The static matches are Markdown formatting, a documented service endpoint, or release decision criteria rather than the alleged threats. The skill also directs deployment record creation and pipeline changes without explicit confirmation, which can affect production evidence.
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
https://skillstore.io/skills/logbrewco-verify-release/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/logbrewco-verify-release?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/logbrewco-verify-release?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/logbrewco-verify-release/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/logbrewco-verify-release.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>logbrewco. (2026). verify-release security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/logbrewco-verify-release/audits/1@techreport{logbrewco-logbrewco-verify-release-2026,
author = {logbrewco},
title = {verify-release security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/logbrewco-verify-release/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "verify-release security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "logbrewco"
date-released: "2026-10-27"
url: "https://skillstore.io/skills/logbrewco-verify-release/audits/1"
identifiers:
- type: other
value: "skillstore:logbrewco-verify-release:audit:1"
description: "Skillstore immutable audit report identifier"
Compare error rates and new issues before continuing a rollout.
Review traffic and failure evidence to decide whether to wait or roll back.
Compare supplied request and error counts when LogBrew tools are unavailable.
Check whether release [release] is safe to continue.
Compare [new release] with [previous release] for [service] in [environment]. Report the evidence and decision.
Compare these equal-length windows: [new counts] and [previous counts]. Include traffic, errors, new error types, and deploy times.
Assess [release] against [previous release] using [team traffic threshold]. Report new issues, normalized error logs, trace rates, limitations, and next checks.
作者
logbrewco授權
MIT
Skillstore 修訂
r1
版本提示
作者未聲明版本。
引用
07bd35e828bc5e79e3fd7ad19a1298e33cdbb753
維護新鮮度
2026/10/27
使用量
0 次下載 · 0 次瀏覽
檔案結構
Debug Production Failures With Evidence
Production failures can be difficult to trace across errors, releases, logs, and affected users. This skill organizes the investigation and verification into seven steps.
Instrument Your App with LogBrew
Application errors and logs can be difficult to trace across deployments. This skill configures LogBrew instrumentation and checks that a test event can be read back.
使用 Application Insights 為 Azure 應用程式加入檢測
由 microsoft
要在不同框架與部署模型中，為託管於 Azure 的應用程式加入可靠的遙測可能很困難。此技能提供精簡的 Application Insights 設定指引、SDK 參考資料，以及 Azure 設定模式。
自動化 DevOps 管線與部署
由 alirezarezvani
DevOps 工作通常需要可重複的管線、基礎架構與部署模式。此技能提供 CI/CD、IaC、部署與營運審查的腳本和參考指南。
透過引導式步驟部署 Kubernetes 工作負載
由 sickn33
Kubernetes 發布需要多個相互協調的產物與檢查。此技能會引導容器準備、manifests、Helm charts、服務網格、安全性、可觀測性與部署驗證。
新增 Python 可觀測性模式
由 0xDarkMatter
Python 服務通常缺乏一致的記錄、指標和追蹤模式。此技能為生產應用程式提供實用的 structlog、Prometheus 和 OpenTelemetry 範例。
協調 DevOps 交付
由 Brownbull
DevOps 工作通常橫跨管線、基礎架構、監控與部署決策。此技能會將這些任務整理成檢查清單、交接事項與推出計畫。
安全產生 Kubernetes 資訊清單
由 sickn33
當團隊憑記憶撰寫 Kubernetes 資訊清單時，很容易設定錯誤。此技能會將需求轉換為結構化 YAML 指引，涵蓋安全性、探針、資源與 Service 模式。