Skip to content

majiayu000/spellbook / skills/release-engineering

release-engineering

Verified

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.

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:
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall