release-workflow

release-workflow is a skill for Claude Code, Codex from Omar-Obando/qwen-orchestrator. It costs 54 tokens per session (2,463 once invoked), scanned A, original, MIT.

A guide to planning how software moves from development into testing and production. CI/CD means automated steps that build, test, and deliver changes; the guide also covers staging environments and rollback plans.

In plain words
What is it for?
Use it to design CI/CD pipelines, release gates, deployment strategies, production monitoring, rollback procedures, checklists, notifications, and release documentation.
Why use it?
It helps make releases repeatable and safer by defining quality checks, approvals, deployment approaches, monitoring, and recovery steps.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design CI/CD pipelines, release gates, deployment strategies, production monitoring, rollback procedures, checklists, notifications, and release documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/omar-obando/qwen-orchestrator/release-workflow
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Omar-Obando/qwen-orchestrator --skill release-workflow
Clone the repo
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestrator

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/release-workflow/github.svg)](https://agentmods.dev/skills/omar-obando/qwen-orchestrator/release-workflow)
Your own site
<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/release-workflow"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/release-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for release-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/release-workflow"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/release-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02463
Opus 5 $0.00027 $0.01231
Sonnet 5 $0.00011 $0.00493
Haiku 4.5 $0.00005 $0.00246

Measured 6d ago against content hash aec9ecabbd24, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

release-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/release-workflow/SKILL.md · 330 lines

How it starts

The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Workflow Skill — Release Manager

Overview

This skill provides comprehensive guidance for designing and implementing release workflows. It covers CI/CD pipelines, staging and production environments, rollback procedures, release gates, and release management best practices following Certified DevOps Engineer and CKA certifications.

When to Use

Use this skill when:

  • Designing release workflows
  • Implementing CI/CD pipelines
  • Managing staging and production environments
  • Creating rollback procedures
  • Ensuring release quality
  • Implementing deployment strategies
  • Creating release gates
  • Managing release documentation
  • Implementing release monitoring
  • Creating release communication plans
  • Managing release dependencies
  • Implementing release testing
  • Creating release checklists
  • Managing release approvals
  • Implementing release automation
  • Creating release rollback strategies
  • Managing release versions
  • Implementing release notifications
  • Creating release reporting
  • Managing release risks
  • Implementing release compliance
  • Creating release training materials
  • Managing release coordination
  • Implementing release optimization

Do NOT use this skill when:

  • Writing application business logic (use domain-driven skill)
  • Designing database schemas (use database-design skill)
  • Writing API endpoint specifications (use api-design skill)
  • Performing security audits (use security-auditor skill)
  • Writing SQL queries (use sql-best-practices skill)
  • Designing multi-page website layouts (use design-system skill)
  • Analyzing deployment configurations (use deployment skill)
  • Writing documentation (use documentation-best-practices skill)

Release Workflow Stages

Release Pipeline

┌─────────────────────────────────────────────────────────────┐
│              Release Pipeline                               │
├─────────────────────────────────────────────────────────────┤
│  1. Code Commit                                             │
│     └── Developer commits code to repository                │
│                                                              │
│  2. Automated Build                                         │
│     └── CI server builds the application                    │
│     └── Runs unit tests                                     │
│     └── Runs static analysis                                │
│                                                              │
│  3. Automated Testing                                       │
│     └── Runs integration tests                              │
│     └── Runs API tests                                      │
│     └── Runs UI tests (if applicable)                       │
│                                                              │
│  4. Quality Gates                                           │
│     └── Code coverage check                                 │
│     └── Security scan                                       │
│     └── Performance benchmark                               │
│                                                              │
│  5. Staging Deployment                                      │
│     └── Deploy to staging environment                       │
│     └── Run smoke tests                                     │
│     └── Run acceptance tests                                │
│                                                              │
│  6. Release Approval                                        │
│     └── Stakeholder approval                                │
│     └── Security review                                     │
│     └── Compliance check                                    │
│                                                              │
│  7. Production Deployment                                   │
│     └── Deploy to production                                │
│     └── Run smoke tests                                     │
│     └── Monitor deployment                                  │
│                                                              │
│  8. Post-Release Monitoring                                 │
│     └── Monitor application health                          │
│     └── Monitor performance                                 │
│     └── Monitor error rates                                 │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 330 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 330 lines · 54 tokens per session scan A aec9ecabbd24

Subscribe to this mod's changes

release-workflow is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 2,463 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

github-release-management

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.

ruvnet/RuView · 27 tokens

releasepr

Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.

compozy/compozy · 53 tokens

gitlab-devops

GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…

automateyournetwork/netclaw · 67 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

seed-snapshot-release

An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.

daangn/seed-design · 19 tokens

push-ci

Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).

sd0xdev/sd0x-harness · 82 tokens