Results for “release-procedure”

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

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.

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.

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.

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

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

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.

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.

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.

Determines whether an app is ready to submit to the App Store, then drives the release flow with asc: validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.

Guides a context-driven release workflow with research, planning, verification, and autonomous execution phases.