Skip to content
cccskills
FreePublished on 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

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

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

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.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

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

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

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.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

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.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

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.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

See all skills by majiayu000

Report a problem with this skill