Results for “release”

Coordinates release preparation for your monorepo — maintaining CHANGELOG and the release assessment document, resolving merge conflicts on release branches, and communicating status, risk, and asks to the broader team. Use when the user mentions release manager, release train, cut a release, release branch, CHANGELOG, release assessment, monorepo release, merge conflicts during release, versioning, or coordinating a version bump with engineering and stakeholders.

The English summary is being prepared. Showing the original description.

Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).

The English summary is being prepared. Showing the original description.

Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"

The English summary is being prepared. Showing the original description.

Prepare and execute Mole CLI releases, from choosing distribution channels and checking tests to publishing version tags. Verify downloadable files, checksums, and the script-based upgrade path, then hand off to the release-notes process.

• Checking whether a Mole CLI release is ready
• Publishing a release with a capital-V tag
• Verifying public downloads and the upgrade path

Draft release notes from commits, pull requests, and file changes since the latest release tag. Update the Unreleased section of CHANGELOG.md with a thematic narrative while preserving previous releases and leaving versions and tags unchanged.

• Keeping release notes current during development
• Summarizing changes before a pull request
• Preparing a changelog draft before release

Prepare and troubleshoot cmux releases by collecting changelog entries, updating versions, checking release readiness, and publishing tags. Follow requirements for macOS disk images, signing, notarization, and update feeds that guide installed apps to new versions.

• Preparing a new cmux release
• Collecting changelog entries from merged PRs
• Troubleshooting a failed pre-tag check

Prepare and publish FastMCP releases, from reviewing changes and crediting contributors to updating changelogs, creating release tags, checking Python package publication on PyPI, and confirming that the documentation site reflects the release.

• Previewing changes for the next FastMCP release
• Preparing release notes and contributor credits
• Publishing a patch or maintenance release

Create a game release checklist tailored to target devices and distribution requirements. Review builds, bugs, store information, and launch preparations, then report readiness while clearly separating known blockers from checks that could not be assessed.

• Check game readiness before release
• Review requirements for a chosen storefront
• Identify release blockers and missing evidence

Guide a macOS app release through versioning, signing, Apple notarization, update feed checks, and Homebrew updates. Includes CodexBar release scripts, published asset verification, and preparation of the next unreleased version.

• Releasing a signed and notarized macOS app
• Verifying update feeds and published release assets
• Updating Homebrew app and CLI packages

Turns Git commits and pull request details into release notes for CHANGELOG.md, a release pull request, and Slack. It categorizes changes, explains user impact in plain language, and flags database migrations that need attention.

• Preparing release notes since the last release
• Summarizing changes across a specified version range
• Drafting a release pull request body

[omh] Shipping a versioned release -- tag it, stage it behind a canary, or roll back the last deploy: decide what goes in, the version, the rollout stages, and a rollback with its trigger and exact command before it is needed. Use when the user says: release-cut, release cut, cut a release, cut the release, cut a new release, tag a release, tag the release, release candidate.

The English summary is being prepared. Showing the original description.

Autonomously cut a Rove (`@sma1lboy/rove`) release end-to-end — detect the semver bump from pending changesets (flagging an upstream `minor` you didn't intend), run the release gates, dispatch the Changesets workflow (or run `scripts/release.sh` locally), then poll the GitHub Actions Release workflow with `gh` until npm publish completes, diagnosing CI failures (npm token, registry 404, lint, branch mismatch) instead of leaving them silent. Use when the user says "cut a release", "ship a version", "release Rove", "release rove", "发版", "release.sh", or "bump the version". Never force-pushes; always verifies the release landed on `main`.

The English summary is being prepared. Showing the original description.

Cut a new Voxt release. Use when the user says "prepare a release", "cut a release", "release Voxt", "do a release", "/prepare-release", or wants to run nbgv prepare-release, bump the version, generate end-user release notes, and announce them in the Releases chat.

The English summary is being prepared. Showing the original description.

Plan a software release cycle with milestones, feature freezes, release candidates, and go/no-go criteria. Covers calendar-based and feature-based release strategies. Use when starting planning for a major or minor version release, transitioning from ad-hoc to structured release cadence, coordinating a release across multiple teams or components, defining quality gates for a regulated project, or planning the first public release (v1.0.0) of a project.

The English summary is being prepared. Showing the original description.

Automate semantic versioning releases with CHANGELOG validation, comparison link management, GitHub Actions workflow triggering, and monitoring. Scaffold release infrastructure for new projects. Use when user runs /release command, mentions "release version", "cut a release", "create release", "publish release", "tag release", "release setup", or "scaffold release pipeline".

The English summary is being prepared. Showing the original description.

Turns a stable Paperclip release changelog into a Discord announcement in dotta’s conversational style. It combines shipped highlights with plans grounded in current work and saves a draft for a person to copy and publish.

• Drafting a Discord announcement for a stable release
• Refreshing an announcement for a new version or date
• Summarizing release highlights and upcoming work

Organize software releases on GitHub, from version suggestions and release notes to testing, builds, and deployment. Coordinate multiple packages or repositories, roll changes out in stages, and configure rollback to restore an earlier release when problems occur.

• Preparing version updates and release notes
• Coordinating releases across packages and repositories
• Deploying in stages with monitoring and rollback

Coordinate software releases on GitHub, from version updates and release notes to testing, builds, deployment, and rollback. It describes workflows using multiple AI agents, including coordinated package releases and gradual deployments with monitoring.

• Prepare version updates and release notes
• Coordinate releases across multiple packages
• Run tests and security checks before release

Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.

• Assess readiness before an npm release
• Check breaking changes and migration needs
• Review version bump recommendations

Prepare and publish Pake releases with version updates, tests, build checks, and verification after publishing. Covers both full releases with GitHub release notes and fixes published only to npm, the package registry.

• Preparing a full Pake release
• Publishing a CLI fix only to npm
• Writing release notes from user-facing changes

Finalize a prepared release by dating and versioning its changelog section, updating configured version files with bumpversion, and creating a release commit and tag. Verify the results and leave them ready to push.

• Finalizing a prepared release
• Applying a patch, minor, or major version increase
• Updating versions across configured project files

Prepare a Python SDK release candidate in a separate working directory, check version metadata and public API compatibility, and produce one local commit with a review report for the release handoff.

• Prepare a manual Python SDK release candidate
• Check release versions and public API compatibility
• Prepare a release pull request handoff

Guide releases of Happy's CLI, mobile app, web app, and server. Choose versions and release channels, follow build and test checks, publish through the designated services, and verify the resulting packages or app updates.

• Publishing a stable or beta CLI release
• Delivering preview or production mobile updates
• Building native apps and submitting to stores

Draft or refresh Omnigent release notes for a specific version and commit range. Review merged pull requests, verify user-facing highlights and contributor credits, and deliver unpublished notes alongside a complete changelog preview.

• Draft release notes before a version tag exists
• Refresh a reviewed draft while preserving editorial changes
• Review breaking changes and upgrade guidance