Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
Install Release Engineering
$ npx skills add majiayu000/spellbook --skill release-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install majiayu000/spellbook release-engineering --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-engineering .claude/skills/release-engineering && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .claude/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/majiayu000/spellbook/tree/main/skills/release-engineeringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add majiayu000/spellbook --skill release-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install majiayu000/spellbook release-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-engineering .agents/skills/release-engineering && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .agents/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add majiayu000/spellbook --skill release-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install majiayu000/spellbook release-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-engineering .cursor/skills/release-engineering && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .cursor/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/majiayu000/spellbook.git --path skills/release-engineering--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add majiayu000/spellbook --skill release-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install majiayu000/spellbook release-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-engineering .gemini/skills/release-engineering && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .gemini/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install majiayu000/spellbook release-engineeringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add majiayu000/spellbook --skill release-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-engineering .github/skills/release-engineering && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .github/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add majiayu000/spellbook --skill release-engineering -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install majiayu000/spellbook release-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-engineering .opencode/skills/release-engineering && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-engineering" agent skill from https://github.com/majiayu000/spellbook/tree/main/skills/release-engineering into .opencode/skills/release-engineering/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-engineering", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-engineering- GitHub stars
- 287
- Token cost
- ~511 tokens
- SKILL.md length
- 165 words
- Files
- 2
- Skills in repo
- 97
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
- Works in 8 steps: Version or release identifier. → Changelog entries grouped by user impact. → Build artifacts and provenance. → …
- Preparing a release
- SKILL.md covers Purpose, Release Classification, Release Plan and Verification, plus 1 more section
- Calls git
What it does
Release Engineering is an agent skill from majiayu000/spellbook. 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.
Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Deployment, Feature launches and release readiness and Changelog and release notes. The repository describes itself as: Cross-runtime skills for Claude Code, Codex, and multi-agent workflows. The licence is MIT.
When your agent uses it
- Preparing a release
- Shipping a risky PR
- Coordinating app/backend/database rollout
- Recovering from a bad deploy
Example prompts
- “/release-engineering”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Version or release identifier.
- Changelog entries grouped by user impact.
- Build artifacts and provenance.
- Migration and config gates.
- Canary or staged rollout plan.
- Monitoring dashboard and alert expectations.
- Rollback or roll-forward command.
- Owner, decision time, and abort criteria.
What it can do on your machine
Read from SKILL.md and the folder at commit ed52af7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Engineering loads about 511 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 165 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from majiayu000/spellbook at commit ed52af7, republished under its MIT licence (© majiayu000). 165 words, ~511 tokens.
Download SKILL.mdSave it as
.claude/skills/release-engineering/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- release-engineering
- description
- 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:
| Type | Extra Gates |
|---|---|
| Patch fix | focused regression test, rollback proof |
| Feature release | feature flag, docs/changelog, product acceptance |
| API or SDK change | versioning, deprecation, compatibility tests |
| Database migration | data-contract-migrations, backup, backfill, recovery |
| Config or secret change | config-secrets-environments, rotation, drift check |
| Infrastructure change | canary, health checks, capacity and rollback |
Release Plan
For non-trivial releases, require:
- Version or release identifier.
- Changelog entries grouped by user impact.
- Build artifacts and provenance.
- Migration and config gates.
- Canary or staged rollout plan.
- Monitoring dashboard and alert expectations.
- Rollback or roll-forward command.
- 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 checkDo 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:© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/release-engineering of majiayu000/spellbook.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit ed52af7
Compare with similar skills
Release Engineering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Engineering this skillmajiayu000/spellbook | 287 | — | ~511 | Automated safety check: Pass | MIT | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Release Orchestratorborghei/Claude-Skills | 886 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Releasebmeares/Meerschaum | 154 | — | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| Agr Releasecomputerlovetech/agr | 451 | — | ~1.6k | Automated safety check: Pass | MIT | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence |
Similar skills
Release Orchestrator
borghei/Claude-Skills
Orchestrate end-to-end release pipelines. An agent skill from borghei/Claude-Skills.
Release
bmeares/Meerschaum
Meerschaum release process — bump version, update changelog, stage dev→main PR, run CI, publish to PyPI, tag, GitHub release, build/push Docker images, rebuild docs on prod VPS.
Agr Release
computerlovetech/agr
Release process for the agr package. An agent skill from computerlovetech/agr.
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
- Official
Devops Rollout Plan
github/awesome-copilot
Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes
More from majiayu000/spellbook
All 97 skills in this repoSkill Ecosystem Doctor
majiayu000/spellbook
Audits and repairs how coding-agent Skills are owned, copied and exposed across runtimes, from canonical sources to quarantine and retirement.
AGENTS.md Scaffold
majiayu000/spellbook
Scans a repository for real evidence and proposes, or on request writes, a small stack of root and scoped AGENTS.md files with validation commands and generated-file boundaries.
Product Demo Builder
majiayu000/spellbook
Plans, produces or diagnoses evidence-backed product demo videos: script, capture plan, pacing checks and verified final media built on real product behavior.
Flowguard Task Guard
majiayu000/spellbook
Single entry point that routes long or ambiguous agent tasks, checks live state, bounds autonomous loops and leaves a resumable handoff.
npm Supply Chain Check
majiayu000/spellbook
Scans a repository, its lockfiles and node_modules for known malicious npm package versions and install-time indicators, using a read-only Python scanner.
Product Manager Toolkit
majiayu000/spellbook
Product management helpers: a RICE scoring script, an interview transcript analyzer and PRD templates for prioritizing features, synthesizing research and writing requirements.
Related
Questions about Release Engineering
What does Release Engineering do?
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Release Engineering is an agent skill from majiayu000/spellbook. Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness.
When should I use Release Engineering?
Release Engineering fits situations like: preparing a release; shipping a risky PR; coordinating app/backend/database rollout; recovering from a bad deploy.
How do I install Release Engineering in Claude Code?
Run `npx skills add majiayu000/spellbook --skill release-engineering -a claude-code`. Or copy the skill folder (skills/release-engineering in majiayu000/spellbook) into .claude/skills/release-engineering in your project. Claude Code loads it when a task matches its description.
How do I install Release Engineering in Codex?
Run `npx skills add majiayu000/spellbook --skill release-engineering -a codex`. Or copy the skill folder (skills/release-engineering in majiayu000/spellbook) into .agents/skills/release-engineering in your project. Codex loads it when a task matches its description.
Can I use Release Engineering in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add majiayu000/spellbook --skill release-engineering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-engineering, .gemini/skills/release-engineering, .github/skills/release-engineering and .opencode/skills/release-engineering in your project.
What does Release Engineering need to run?
Going by SKILL.md and its folder, Release Engineering needs the command-line tools its instructions call (git).
Does Release Engineering access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Engineering safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Engineering use?
Release Engineering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Engineering use?
About 511 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Engineering?
Skills that share tags, products or a category with Release Engineering: Release Maintainer (Undertone0809/rudder, 292 stars), Release Orchestrator (borghei/Claude-Skills, 886 stars), Release (bmeares/Meerschaum, 154 stars) and Agr Release (computerlovetech/agr, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Engineering?
majiayu000 (a GitHub user) maintains it in majiayu000/spellbook, which has 287 GitHub stars. The repository holds 97 skills in this directory. The repository was last updated on October 8, 2026.
Source: majiayu000/spellbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.