本文へ移動
cccskills
無料GitHub で公開

release-engineering

Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release policy for a repo.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.0 KB
  • agents/openai.yaml234 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Release Engineering

Purpose

Use this skill to turn "ready to merge" into a controlled release. It connects code, data, config, deployment, monitoring, and rollback.

Release Classification

Classify the release before choosing gates:

TypeExtra Gates
Patch fixfocused regression test, rollback proof
Feature releasefeature flag, docs/changelog, product acceptance
API or SDK changeversioning, deprecation, compatibility tests
Database migrationdata-contract-migrations, backup, backfill, recovery
Config or secret changeconfig-secrets-environments, rotation, drift check
Infrastructure changecanary, health checks, capacity and rollback

Release Plan

For non-trivial releases, require:

  1. Version or release identifier.
  2. Changelog entries grouped by user impact.
  3. Build artifacts and provenance.
  4. Migration and config gates.
  5. Canary or staged rollout plan.
  6. Monitoring dashboard and alert expectations.
  7. Rollback or roll-forward command.
  8. Owner, decision time, and abort criteria.

Verification

Use fresh commands from the current session. Typical gates:

git status --short
git log --oneline -n 5
# project-specific build/test command
# migration dry run or validation query
# deployment health check

Do not claim a release shipped unless remote git, CI, artifact, and runtime state have each been checked at the required level.

Output Shape

release_scope:
version_or_identifier:
included_changes:
excluded_changes:
pre_release_checks:
rollout_steps:
migration_and_config_gates:
monitoring:
rollback_or_recovery:
go_no_go_status:

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

日本語の概要は準備中です。原文の説明を表示しています。

majiayu000/spellbook2872026年10月8日 更新

majiayu000 のスキルをすべて見る

このスキルの問題を報告する