Results for “release-procedure”

Use when the user asks to release, version, tag, or publish.

Routes legacy release-manager references to the current runtime capability, preferring matching agents or modern plugin skills.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Automates the full release workflow for a single-package GitHub repository, from analysis through changelog authoring and PR creation using gh and git.

Prepare and verify a staged or production deployment with rollback and smoke checks.

Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up.

Release Manager

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release

Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.

Begins a new version release using git-flow. This skill should be used when the user asks to "start a release", "create release branch", "prepare a release", "git flow release start", or wants to begin a new version release. Accepts either an explicit version or a natural-language description of the release.

Agent skill for release-swarm - invoke with $agent-release-swarm

Coordinates multi-service releases, manages container registries, and sets up CI/CD pipelines across platforms.

Weline_Deploy：随机 Webhook 路径（~wh~）、ModuleRouter、webhook_secret、 deploy:webhook:setup、deploy:release、WLS+Nginx。

`analysis-agent`/`task-agent`/`review-agent`: use for release identity, compatibility, exposure, stop, rollback, or recovery; skip pipeline-only and no-release work.

Use this skill for release readiness, rollback plans, changelogs, deployment checks, production risk. Trigger when the task involves agent profile work related to Release Manager Agent, implementation, audits, debugging, strategy, or validation.

Cut releases, validate changelogs, and manage git hooks for a project.

Full release pipeline — tests → coverage → review gate → version bump → CHANGELOG → commit → PR

Use the release-audit skill to run the pre-release validation sweep and print

Automates project releases with version bumping, multi-language changelog generation, and GitHub Release creation. Supports Node.js, Python, Rust, and generic projects.

Fork, sanitize, and package private projects for safe public release through a three-stage pipeline.

Composite skill — promote the long-lived `release` branch to `main`, cut a single version that batches every PR accumulated since the last tag, then clean up. Chains pr-merge-readiness (on release→main PR) → version-bump (semver from commits) → changelog-update (promote [Unreleased] → versioned) → ship (tag + GitHub release) → stale-branch cleanup → optional ship-it for deploy. Use this INSTEAD of releasing every small fix individually. Many small commits become one well-scoped release.

Prepare release readiness notes, version checks, test checklist, and local issue drafts.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Release npm packages end-to-end: Changesets version bump, CHANGELOG update, GitHub Actions OIDC publish, and post-release verification. Use when the user says "release to npm", "publish this package", "ship a new version", "cut a release", "update the changelog", or combines a package name with a release verb.

Enforces the complete release checklist for ClawRouter: version sync, CHANGELOG, build, tests, npm publish, git tag, and GitHub release, with no steps skipped.

PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering

Generates the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

Executes multi-stage release plans by reading a PHASE-PLAN.md, implementing each stage, running validation and critique gates, committing with clean scope, and advancing automatically, halting on repeated failures or unresolvable issues.

Fencang Release

Ship validated changes with repeatable release evidence — version bump, changelog, tag, and optional GitHub release

Use `analysis-agent` for release decisions, `task-agent` for delivery artifacts, or `review-agent` for readiness on deployment, migration, rollback, or production risk. Skip local work with no release decision.

Drafts a HIPAA Release Authorization form compliant with 45 CFR § 164.508 for authorizing disclosure of protected health information. Use when drafting HIPAA authorizations, PHI release forms, medical records releases, or healthcare privacy waivers alongside healthcare powers of attorney or advance directives.

CI release engineer skill for validation gating, release-readiness checks, and automation-safe delivery criteria.