verify-release
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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„verify-release“ wird verwendet. Assess a release with sufficient traffic and stable error rates.
Erwartetes Ergebnis:
Decision: Go. Both releases have sufficient traffic, and the observed error rates are unchanged. No new issue affects a main user flow.
„verify-release“ wird verwendet. Assess a release with too few traces for comparison.
Erwartetes Ergebnis:
Decision: Wait. The new release has too little traffic for a reliable comparison. Recheck trace counts and error rates after more requests.
Sicherheitsaudit
Mittleres RisikoThe 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.
Bestätigte Sicherheitsbedenken (1)
Risikofaktoren
⚙️ Externe Befehle (30)
🌐 Netzwerkzugriff (1)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/logbrewco-verify-release/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/logbrewco-verify-release?utm_source=security_passport_badge)HTML-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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
logbrewco. (2026). verify-release security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/logbrewco-verify-release/audits/1BibTeX-Zitat
@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}
}CITATION.cff
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"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Assess a production rollout
Compare error rates and new issues before continuing a rollout.
Investigate a canary
Review traffic and failure evidence to decide whether to wait or roll back.
Review exported counts
Compare supplied request and error counts when LogBrew tools are unavailable.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- Compare the same service and environment across equal-length windows.
- Normalize error counts by traffic and apply your team traffic threshold.
- Review limitations and verify deployment details before recording them.
Vermeiden
- Do not treat missing telemetry as zero errors.
- Do not assume a release caused an error solely because it preceded the error.
- Do not create deployment records or modify pipelines without confirming the details and authorization.
Häufig gestellte Fragen
What decisions can the skill recommend?
Can I use it without LogBrew?
Does the skill prove a release caused an error?
How much traffic is enough?
Can the MCP server record deployments?
Does the skill perform a rollback?
Entwicklerdetails
Autor
logbrewcoLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
07bd35e828bc5e79e3fd7ad19a1298e33cdbb753
Aktualität der Wartung
27.10.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur