스킬 verify-release

📦

verify-release

Name: verify-release
Author: logbrewco

콘텐츠 리비전 r1 중간 위험 ⚙️ 외부 명령어🌐 네트워크 접근

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.

지원: Claude Codex Code(CC)

📊 65 적절함

Maintain this Skill? Claim it 📊 65 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 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 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/logbrewco-verify-release.md 서명된 manifest GET /api/skills/logbrewco-verify-release/manifest 서명된 lockfile GET /api/skills/logbrewco-verify-release/lockfile

테스트해 보기

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

보안 감사

중간 위험

v1 • 2026. 10. 27. 버전별 보고서 열기

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.

스캔된 파일

184

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

SKILL.md:40-50 SKILL.md:73-74

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.

위험 요인

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

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

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)

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>

임베드 카드

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

학술 인용 (APA · BibTeX · CFF)

APA 인용

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

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"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

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.

이 프롬프트를 사용해 보세요

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.

모범 사례

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.

피하기

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.

자주 묻는 질문

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.

개발자 세부 정보

작성자

logbrewco

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

https://github.com/logbrewco/skills/tree/abac3ee500d980ca7fa4edb6c75949094d3ea792/plugins/logbrew/skills/verify-release

참조

07bd35e828bc5e79e3fd7ad19a1298e33cdbb753

유지보수 최신성

2026. 10. 27.

사용량

0 다운로드 · 0 조회

파일 구조

📁 references/

📄 operations.md

📄 SKILL.md

logbrewco의 다른 스킬

전체 보기

📦

Kubernetes Manifest를 안전하게 생성하기

작성자 sickn33

팀이 기억에 의존해 Kubernetes manifest를 작성하면 잘못 구성하기 쉽습니다. 이 skill은 요구사항을 보안, probes, resources, service 패턴을 포함한 구조화된 YAML 가이드로 전환합니다.

DevOps 및 인프라 보기