2천건 · 관련도순
Coordinate a game release from candidate preparation through testing, release approval, and deployment. Assign work to role-based agents and collect quality results, patch notes, launch messaging, and a post-release monitoring plan.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Publish an OpenWork version through Git tags and GitHub Actions without creating version-update commits. Review outstanding fixes, monitor builds and publication, check release assets, and recover failed distribution steps using procedures that protect already published desktop installers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Test a released archon binary through Homebrew or curl installation on macOS or a Linux VPS. Check version information, bundled workflows, Claude execution, and sensitive environment key removal, then clean up and report the results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Scaffold or migrate a repository onto release-please. Generates release-please-config.json, .release-please-manifest.json, and a release-please.yml workflow, plus an opt-in menu of tag-keyed deploy/publish templates (Docker/ECR matrix, frontend host deploy, npm OIDC publish, GitHub Release asset, Fly.io deploy, generic). Supports monorepo (mutual exclude-paths matrix), single-package, and mixed-language (node/simple/python) repos. Use when user runs /release-please-setup, mentions "release please", "set up release please", "automate releases", "conventional-commit releases", "monorepo release automation", or "migrate to release-please".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare a Python SDK release plan or candidate with the previous release to assess compatibility, versioning, and proven regressions. Produce a ship-or-block recommendation, documentation handoff, and key changes for minor releases.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Update a project's changelog using GitHub releases, git history, and code differences. Select changes that matter to users, match the existing format, and write concise entries for the requested release.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides a Worktrunk release from testing and change review to version updates, release notes, tagging, and publication checks. Includes reviews of potential data loss, documentation accuracy, and contributor credits before the release is published.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the Tamanu release-branch CUTOFF checks when preparing to cut a new release/X.YY branch: confirm the previous release's hotfixes are merged to main, reconcile the commits since the previous release against the "Merged to main" card list from Linear, and scan for data/reporting/schema changes. Use when the user is cutting a Tamanu release and wants to verify the codebase is ready, wants to check main against the previous release branch, or wants to reconcile commits with a Linear "Merged to main" column (they should paste the card list). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for verifying an existing release branch's hotfix integrity (see pre-release-checks) or for deciding which tests to run (see scope-tamanu-release-tests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OpenClaw 출시 정보를 확인해 Discord 공지를 작성합니다. 버전별 업데이트 절차와 사용자 테스트 항목을 정리하고 승인 후 게시도 지원합니다.
Delegate a coding task to a subagent that runs build, merges the ready pull request, and continues from the updated main branch into release, connecting implementation and release work in one automated sequence.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.