Compétences verify-release
📩

verify-release

RĂ©vision du contenu r1 Risque moyen ⚙ Commandes externes🌐 AccĂšs rĂ©seau

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.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it 📊 65 AdĂ©quat

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Tester

Utilisation de « verify-release ». Assess a release with sufficient traffic and stable error rates.

Résultat attendu:

Decision: Go. Both releases have sufficient traffic, and the observed error rates are unchanged. No new issue affects a main user flow.

Utilisation de « verify-release ». Assess a release with too few traces for comparison.

Résultat attendu:

Decision: Wait. The new release has too little traffic for a reliable comparison. Recheck trace counts and error rates after more requests.

Audit de sécurité

Risque moyen
v1 ‱ 27/10/2026 Ouvrir le rapport versionnĂ©

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.

2
Fichiers analysés
184
Lignes analysées
0
ÉlĂ©ments Ă  examiner
0
Faux positifs ignorés

Préoccupations de sécurité confirmées (1)

Moyen
Deployment records may be changed without confirmation
The skill instructs the agent to record missing deployments as succeeded and add a command to the pipeline without requiring user confirmation. Incorrect records or pipeline changes can distort release comparisons.
The instructions explicitly request a state-changing deployment record and pipeline modification, but do not require confirmation or verification of successful status.
Audité par: codex
Partager et citer ce rapport

Partagez le rapport d’évaluation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.

Ouvrir le rapport versionné
Évaluation de sĂ©curitĂ©

Copier le lien du rapport

https://skillstore.io/skills/logbrewco-verify-release/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/logbrewco-verify-release/security.svg)](https://skillstore.io/skills/logbrewco-verify-release?utm_source=security_passport_badge)

Badge HTML

<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>

Carte intégrable

<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>
Citations académiques (APA · BibTeX · CFF)

Citation APA

logbrewco. (2026). verify-release security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/logbrewco-verify-release/audits/1

Citation BibTeX

@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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen
41
Architecture
85
Maintenabilité
85
Contenu
65
Communauté
83
Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

Basic release check
Check whether release [release] is safe to continue.
Compare releases
Compare [new release] with [previous release] for [service] in [environment]. Report the evidence and decision.
Use exported counts
Compare these equal-length windows: [new counts] and [previous counts]. Include traffic, errors, new error types, and deploy times.
Review a rollout
Assess [release] against [previous release] using [team traffic threshold]. Report new issues, normalized error logs, trace rates, limitations, and next checks.

Bonnes pratiques

  • 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.

Éviter

  • 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.

Foire aux questions

What decisions can the skill recommend?
It recommends Go, Rollback, or Wait based on available release evidence.
Can I use it without LogBrew?
Yes. Provide request counts, error counts, new error types, and deploy times for equal-length windows.
Does the skill prove a release caused an error?
No. The comparison provides evidence, but deployment order does not prove causality.
How much traffic is enough?
The default is at least 100 traces per release in the compared window. A team threshold can replace it.
Can the MCP server record deployments?
No. The skill describes the MCP server as read-only; recording requires CLI account access.
Does the skill perform a rollback?
The documented workflow recommends a decision. It does not provide a command to perform a rollback.

Détails du développeur

Auteur

logbrewco

Licence

MIT

Révision Skillstore

r1

Avis de version

L’auteur n’a dĂ©clarĂ© aucune version.

Réf

07bd35e828bc5e79e3fd7ad19a1298e33cdbb753

Récence de maintenance

27/10/2026

Utilisation

0 téléchargements · 0 vues

Structure de fichiers

📁 references/

📄 operations.md

📄 SKILL.md

Autres compétences de logbrewco

Tout afficher
Tout afficher