본문으로 건너뛰기
cccskills
무료GitHub에 공개

release-engineering

Prepares and controls software releases with risk classification, CI quality gates, artifact provenance, feature flags, staged rollout, measurable promotion and rollback thresholds, post-deploy verification, and cleanup. Use for deployment pipelines, launch readiness, canaries, production rollout, release automation, or rollback planning. Not for merely merging a completed development branch or proving one local change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md2.7 KB
  • agents/openai.yaml223 B
  • references/post-deploy-verification.md1.2 KB
  • references/release-record.md852 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Release Engineering

Turn a release into a sequence of evidence-backed decisions rather than one irreversible event.

Build the release contract

Record the artifact/version, environments, owner, change scope, affected users, data or contract changes, dependencies, risk class, maintenance window, and success metrics. Use release-record.md for the go/no-go and rollout record.

Establish gates

Require checks proportional to risk: build and tests, contract and migration proof, security findings, performance budgets, smoke paths, accessibility or visual checks, artifact signing/provenance, monitoring, and a tested recovery path. A green generic pipeline is not proof of the release's critical behavior.

Roll out safely

  1. Separate deployment from exposure with a flag or routing control when practical.
  2. Start with internal, shadow, canary, or low-percentage traffic.
  3. Compare errors, latency, saturation, business outcomes, and support signals against a pre-release baseline.
  4. Promote only after the observation window and all gates pass.
  5. Roll back or disable immediately when a predefined threshold is crossed.
  6. Verify recovery, communicate status, and preserve the timeline.

For canaries and production observation windows, use post-deploy-verification.md. Confirm the deployed build marker, run critical browser journeys through browser-testing, and record each promote, hold, or rollback decision against fresh baseline evidence.

Use immutable artifacts across environments. Keep release credentials out of logs and command lines. Require explicit authority for production mutation.

Close the release

Verify critical paths after deployment, monitor delayed jobs and regional effects, remove stale flags and compatibility paths on schedule, update release notes, and create owned follow-ups for non-blocking debt. Never substitute a successful deployment command for an observation window. Use incident-response if live impact begins and safe-migrations for stateful cutovers.

Completion condition

The intended artifact reached the intended audience, promotion evidence and remaining limits are recorded, rollback readiness was real, and temporary release controls have owners and expiry dates.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode982026년 8월 26일 업데이트

thiientv의 스킬 모두 보기

이 스킬의 문제 신고