Broken API Interviewer
PrepLabsAI/InterviewMentor
An on-call SRE interviewer who just got paged about a broken checkout API.
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags…
Install Release Engineering
$ npx skills add magnus919/agent-skills --skill release-engineering -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills 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/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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/magnus919/agent-skills/tree/main/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 magnus919/agent-skills --skill release-engineering -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills release-engineering --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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 magnus919/agent-skills --skill release-engineering -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills release-engineering --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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/magnus919/agent-skills.git --path 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 magnus919/agent-skills --skill release-engineering -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills release-engineering --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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 magnus919/agent-skills 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 magnus919/agent-skills --skill release-engineering -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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 magnus919/agent-skills --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 magnus919/agent-skills release-engineering --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/magnus919/agent-skills/tree/main/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
- 113
- Token cost
- ~3.9k tokens
- SKILL.md length
- 1,454 words
- Files
- 42 (incl. scripts, references, assets)
- Skills in repo
- 115
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags…
- Application feature implementation (backend-engineering/frontend-engineering)
- SKILL.md covers Ownership, Core Principles, Loading Guide and Adjacent Skills, plus 4 more sections
- Calls python3
- Production incident root-cause debugging
What it does
Release Engineering is an agent skill from magnus919/agent-skills. Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination. Do not use for application feature implementation…
Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 44 other files, including scripts, reference files and assets (for example `README.md`, `assets/deployment-strategy-matrix.md` and `assets/dora-metrics-reference.md`). Compatibility notes: Platform-agnostic methodology. Scripts require Python 3.8+ (stdlib only). No CI platform, deployment tool, or version control mandate.
It sits in DevOps & Cloud, covering Site reliability engineering, Platform engineering and Debugging. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- Application feature implementation (backend-engineering/frontend-engineering)
- Production incident root-cause debugging
- On-call/SLO operations (systematic-debugging / site-reliability-engineering)
- Security implementation
Example prompts
- “/release-engineering”
Requirements
- Python 3
- Compatibility (from SKILL.md): Platform-agnostic methodology. Scripts require Python 3.8+ (stdlib only). No CI platform, deployment tool, or version control mandate.
What it can do on your machine
Read from SKILL.md and the folder at commit 96fbe07. 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
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.
Compatibility
Platform-agnostic methodology. Scripts require Python 3.8+ (stdlib only). No CI platform, deployment tool, or version control mandate.
From compatibility in the SKILL.md frontmatter.
Context cost
Release Engineering loads about 3.9k tokens when it runs, and up to ~82k if it reads all its reference files. Until then it costs about 209 tokens; SKILL.md has 1,454 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); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/agent-skills at commit 96fbe07, republished under its MIT licence (© magnus919). 1,454 words, ~3,883 tokens.
Download SKILL.mdSave it as
.claude/skills/release-engineering/SKILL.md (or your agent's skills folder). This skill also uses 41 other files; get the full folder from GitHub.- name
- release-engineering
- description
- Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination. Do not use for application feature implementation (backend-engineering/frontend-engineering), production incident root-cause debugging or on-call/SLO operations (systematic-debugging / site-reliability-engineering), security implementation or threat modeling (secure-software-engineering), or internal developer platform construction (platform-engineering).
- compatibility
- Platform-agnostic methodology. Scripts require Python 3.8+ (stdlib only). No CI platform, deployment tool, or version control mandate.
- license
- MIT
- metadata.source_repo
- https://github.com/magnus919/agent-skills
- metadata.skill_version
- 1.0.0
- metadata.tags
- release-engineering, releases, ci-cd, continuous-delivery, progressive-delivery, feature-flags, semver, changelog, rollback, release-trains, dora, sbom…
Release Engineering
Senior-to-principal release engineering methodology: designing and operating the pipelines, processes, artifacts, gates, compliance evidence, and metrics that move software from commit to customer safely, predictably, and fast.
Ownership
| You own | You don't own |
|---|---|
| Release process design — branch strategy, process model, release cadence | Application feature implementation — route to backend-engineering / frontend-engineering |
| CD pipeline architecture — build-once promotion stages, gates, push-on-green | Production incident root-cause debugging — route to systematic-debugging |
| Progressive delivery — canaries, rings, percentage rollouts, feature flags | On-call and SLO operations — route to site-reliability-engineering |
| Versioning and artifacts — SemVer, conventional commits, changelogs, immutability, provenance | Security implementation and threat modeling — route to secure-software-engineering |
| Readiness and quality gates — release candidates, go/no-go, sign-off | Internal developer platform construction — route to platform-engineering |
| Rollback and recovery planning — runbooks, rehearsals, recovery targets | Data pipeline operations and schema migration engineering — route to data-engineering |
| Change governance and audit compliance — SOC 2 / SOX / PCI evidence chains | Spec authoring and SDD gate mechanics — route to spec-driven-development |
| DORA metrics — definitions, computation, thresholds | API contract design and versioning policy — route to api-design-and-evolution |
| Multi-team release coordination — trains, calendars, stabilization | Evidence collection and verdicts against explicit criteria — route to verification-methodology |
| Release operations — branch cuts, pipeline triage, emergency releases | Runtime monitoring and alerting — that's SRE |
Core Principles
Build once, promote many. The artifact that passed every gate is the only artifact that ships. Rebuilding per environment reintroduces risk and invalidates what was verified.
Small batches ship faster and safer. Trunk-based development with frequent small merges outperforms long-lived branches on every DORA metric — deployment frequency, lead time, change failure rate, and recovery time.
Decouple deploy from release. Deploying code to production is not the same as exposing it to users. Feature flags and progressive rollout separate the two so each can happen on its own timeline and either can be reversed independently.
Automated safety beats approval bureaucracy. Evidence-based controls and pipeline gates outperform change-advisory-board sign-off, which research correlates with slower, less stable delivery. Automate the checks; reserve human approval for genuinely exceptional change.
Rehearse rollback. A rollback you haven't practiced will fail under pressure. Rollback is a first-class release artifact with its own runbook, trigger thresholds, and rehearsal log.
Verify in production. Staging parity helps, but production canaries, smoke tests, and observability gates are where readiness is actually proven. Real traffic, real telemetry, real decision points.
Protect the supply chain. Sign every artifact, record provenance and SBOM data, and treat registries as a security boundary. Integrity is part of the release, not an add-on.
DORA is a system outcome. Speed and stability emerge from how the process is designed — batch size, architecture, automation, safety culture — not from chasing metric targets.
Loading Guide
| File | Load when |
|---|---|
references/role-and-career.md | Understanding the release engineering role — org placement, day-to-day, Senior/Staff/Principal leveling, and evidence separating levels |
references/skills-competency-model.md | Mapping the technical and professional skills release engineers master, and which ones differentiate at senior and above |
references/release-process-models.md | Choosing a process model — trunk-based, GitFlow, GitHub Flow, release branches, release trains — and matching cadence to the org |
references/cd-and-pipeline-stages.md | Designing CD pipelines — build-once promotion, stage gates, push-on-green, pipeline-as-code, hermetic builds, environment parity |
references/progressive-delivery.md | Planning canary, blue/green, ring, or percentage rollouts; metric and error-budget gates; auto-rollback triggers |
references/change-governance-and-compliance.md | Building audit-ready change control — SOC 2 CC8.1, SOX ITGC, PCI back-out, evidence chains, separation of duties, emergency change |
references/readiness-and-quality-gates.md | Defining readiness dimensions, release candidates, go/no-go structure, error-budget release policy, definition of done |
references/rollback-and-recovery.md | Planning rollback vs roll-forward vs flag recovery per system type; rehearsed rollbacks; time-boxed decisions; quarantine |
references/versioning-and-artifacts.md | Setting SemVer/CalVer policy, conventional commits, changelog conventions, artifact immutability and provenance |
references/feature-flag-lifecycle.md | Running flags through their full lifecycle — create, guard, rollout, verify, remove, expire — and avoiding flag debt |
references/monorepo-polyrepo-release.md | Choosing mono vs polyrepo release strategy, affected-build detection, topological publish order, release tooling |
references/toolchain-landscape.md | Selecting tools by category — CI/CD, release automation, artifact repos, GitOps, feature flags (2025-2026 status) |
references/supply-chain-security.md | Hardening the supply chain — SLSA, SBOM, sigstore keyless signing, dependency updates, provenance attestations |
references/metrics-and-dora.md | Defining and computing the five DORA metrics, thresholds, vendor divergence, and measurement pitfalls |
references/release-operations-and-triage.md | Running release trains end-to-end — branch cuts, stabilization, go/no-go, pipeline triage, release infra reliability, agentic automation |
templates/release-plan.md | Producing a release plan — scope, milestones, owners, risks, rollout, rollback contingency, comms |
templates/release-readiness-checklist.md | Running a readiness review — checkbox table by dimension with owner + evidence, go/no-go block |
templates/rollback-runbook.md | Writing a rollback runbook — triggers, per-layer steps, verification, ordering, comms, rehearsal log |
templates/release-notes.md | Drafting release notes — version, date, change-type sections, breaking changes, migration steps |
templates/change-governance-record.md | Recording an audit-ready change — ticket, PR, CI runs, artifact digest, deploy timestamp, verification, emergency flag |
templates/hotfix-emergency-release-plan.md | Planning an emergency release — severity, break-glass approvals, expedited path, post-implementation review |
assets/dora-metrics-reference.md | Looking up the five DORA metrics — formulas, units, data sources, thresholds, pitfalls — in one page |
assets/versioning-decision-table.md | Choosing a versioning scheme — SemVer vs CalVer vs independent vs one-version, bump rules |
assets/deployment-strategy-matrix.md | Comparing deployment strategies — rolling, blue-green, canary, ring, flag, shadow — on speed, safety, rollback |
assets/release-toolchain-cheatsheet.md | Quick tool lookup by category — one-liner and when-to-pick per tool |
scripts/version_bump.py | Computing the next SemVer from conventional commits or a git range |
scripts/semver_check.py | Validating, comparing, or sorting strict SemVer versions |
scripts/changelog_check.py | Validating Keep a Changelog or Release Please CHANGELOG.md files |
scripts/dora_metrics.py | Computing the five DORA metrics from deployment and commit event data |
scripts/release_plan_scaffold.py | Scaffolding a release plan document from flags or a git range |
evals/evals.json | Running output-quality evals for this skill (schema v1, 8 cases) |
Show full SKILL.md (589 more words)Show less
Adjacent Skills
- Use qa-methodology to define test strategy, regression scope, flake policy, and quality-gate semantics. This skill combines the resulting evidence with operational and governance evidence for a release decision.
- For AI-agent releases, use agent-evals-and-observability to design and interpret behavioral, trajectory, and model-regression evidence before incorporating it into a release gate.
Scripts
| Script | Invocation | Purpose |
|---|---|---|
| version_bump | python3 scripts/version_bump.py --current-version 1.4.0 --git-range v1.4.0..HEAD | Computes the next SemVer from Conventional Commits — breaking → major (minor in 0.x), feat → minor, fix → patch; optional prerelease tag |
| semver_check | python3 scripts/semver_check.py --check 1.2.3-beta.1 | Validates strict SemVer 2.0.0, compares two versions, or sorts a list |
| changelog_check | `python3 scripts/changelog_check.py CHANGELOG.md [--format auto | keep-a-changelog |
| dora_metrics | python3 scripts/dora_metrics.py --events events.json | Computes all five DORA metrics from deployment and commit event data |
| release_plan_scaffold | python3 scripts/release_plan_scaffold.py --version 2.0.0 --owner alice --output plan.md | Scaffolds a release plan document with filled placeholders from flags or a git range |
Triggers
Load this skill when the task involves:
- Release planning — designing a release plan, timeline, milestones, or rollout strategy
- Pipeline design — architecting or reviewing CD pipelines, promotion stages, or push-on-green
- Version bumps — computing the next version, SemVer validation, conventional-commit classification
- Changelogs — authoring or validating a changelog
- Readiness review — go/no-go calls, release candidates, readiness checklists
- Rollback planning — writing or rehearsing rollback runbooks and recovery plans
- Progressive delivery — canaries, rings, percentage rollouts, traffic shadowing
- Feature flags — flag rollout, lifecycle, and cleanup
- Release trains — calendar releases, branch cuts, stabilization windows
- DORA metrics — defining, computing, or reporting the five DORA metrics
- Compliance evidence — SOC 2 / SOX / PCI change records, audit trails, separation of duties
- Artifacts and supply chain — SBOM, provenance, signing, registry hygiene
- Emergency releases — hotfixes, break-glass changes, expedited release paths
- Multi-team coordination — cross-team release calendars and integration stabilization
When not to use
Route to the named sibling skill instead:
- backend-engineering / frontend-engineering — implementing application features. Release engineering designs the pipeline that ships code; it does not implement the code itself.
- systematic-debugging — root-cause analysis of production incidents, fault localization, bug reproduction. Release engineering plans recovery; debugging finds the cause.
- site-reliability-engineering — on-call operations, SLO/error-budget management, capacity planning, and day-to-day incident response.
- secure-software-engineering — security implementation and threat modeling. Release engineering consumes security controls (SBOM, signing, dependency scanning) but does not design them.
- platform-engineering — building the internal developer platform: CI infrastructure, GitOps controllers, self-service tooling, and golden paths.
- data-engineering — data pipeline operations, schema migration engineering, and data quality monitoring.
- spec-driven-development — writing specifications and running SDD pipeline gates and verdicts.
- api-design-and-evolution — API contract design and versioning policy. Release engineering version-bumps artifacts; it does not set API evolution rules.
- verification-methodology — collecting evidence and rendering verdicts against explicit pass/fail criteria.
Stop and Exit Conditions
- Release plan complete when: the plan names version, target date, milestones and branch cut, owners (RACI), scope items, risks with mitigations, rollout plan, rollback contingency, comms plan, and sign-offs.
- Readiness checklist complete when: every item in each dimension (functional, non-functional, operational, governance) has an owner and evidence, and a go/no-go decision is recorded.
- Rollback runbook complete when: trigger thresholds, impact assessment, decision criteria, per-layer rollback steps, verification SLIs, rollback ordering, comms, and a rehearsal log are all in place.
- Version bump complete when: the next version is computed from actual commit history (or an explicit file), validated against strict SemVer, and the bump rule is justified by the conventional-commit types.
- Compliance record complete when: the change chain — ticket → PR review → CI → approval → deploy log → verification — is complete, sampled, and retained per policy, with separation of duties respected.
- Bounded escalation: stop after three non-converging diagnostic passes and report the evidence collected so far.
© magnus919, 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 41 other files (scripts, references, assets) in release-engineering of magnus919/agent-skills.
- SKILL.md
- README.md
- assets/deployment-strategy-matrix.md
- assets/dora-metrics-reference.md
- assets/release-toolchain-cheatsheet.md
- assets/versioning-decision-table.md
- evals/evals.json
- pytest.ini
- references/cd-and-pipeline-stages.md
- references/change-governance-and-compliance.md
- references/feature-flag-lifecycle.md
- references/metrics-and-dora.md
- references/monorepo-polyrepo-release.md
- references/progressive-delivery.md
- references/readiness-and-quality-gates.md
- references/release-operations-and-triage.md
- references/release-process-models.md
- references/role-and-career.md
- … and 24 more
Open the folder on GitHubat commit 96fbe07
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 skillmagnus919/agent-skills | 113 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Broken API InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Release Itwondelai/skills | 2.4k | — | ~4k | Automated safety check: Pass | MIT | |
| Delivery Managerborghei/Claude-Skills | 881 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Aspiremicrosoft/aspire.dev | 196 | 4 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Release It
wondelai/skills
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic.
Delivery Manager
borghei/Claude-Skills
Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.
- Official
Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
Borg Live Debug
karanhudia/borg-ui
Live Borg debugging by exec-ing into the borg-web-ui Docker container.
More from magnus919/agent-skills
All 115 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Related
Categories
Questions about Release Engineering
What does Release Engineering do?
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags…. Release Engineering is an agent skill from magnus919/agent-skills. Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination.
When should I use Release Engineering?
Release Engineering fits situations like: application feature implementation (backend-engineering/frontend-engineering); production incident root-cause debugging; on-call/SLO operations (systematic-debugging / site-reliability-engineering); security implementation.
How do I install Release Engineering in Claude Code?
Run `npx skills add magnus919/agent-skills --skill release-engineering -a claude-code`. Or copy the skill folder (release-engineering in magnus919/agent-skills) 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 magnus919/agent-skills --skill release-engineering -a codex`. Or copy the skill folder (release-engineering in magnus919/agent-skills) 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 magnus919/agent-skills --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 (python3). Our summary lists: Python 3. Compatibility (from SKILL.md): Platform-agnostic methodology. Scripts require Python 3.8+ (stdlib only). No CI platform, deployment tool, or version control mandate..
Does Release Engineering access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release Engineering use?
Release Engineering is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Engineering use?
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 78k tokens, read only when the agent opens those files.
What are the alternatives to Release Engineering?
Skills that share tags, products or a category with Release Engineering: Broken API Interviewer (PrepLabsAI/InterviewMentor, 112 stars), Devops Engineer (Yikai-Liao/symusic, 189 stars), Release It (wondelai/skills, 2.4k stars) and Delivery Manager (borghei/Claude-Skills, 881 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Engineering?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 113 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on October 6, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.