'release' 검색 결과

Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run automated checks on the actual release branch
• Check whether a PR merges into the release branch
• Manually test terminal responsiveness and input behavior

Prepare a library release on GitHub by reviewing code changes, proposing a version number, drafting a changelog, and opening a release pull request. Version and changelog reviews let you confirm the details before proceeding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing the next version from public API changes
• Drafting a changelog for library users
• Preparing a release branch and pull request

Prepare batches of merged SGLang pull requests for a release branch. It checks conflicts and previous attempts, starts the cherry-pick workflow, monitors completion, and reports created pull requests or failure reasons.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare multiple merged PRs for a release branch
• Check conflicts before starting workflows
• Detect previous cherry-pick PRs

Prepare a deployment checklist covering tests, approvals, database changes, release steps, and monitoring. Tailor it to the release and document rollback triggers, the conditions for reverting a change, before production deployment begins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare checks for an upcoming production release
• Review a release with database migrations
• Verify feature flags and CI status before deployment

Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare an end-of-day release handoff
• Consolidate documentation for merged changes
• Review unfinished work and verification status

Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a desktop app release
• Checking whether Rust changes require a CLI release
• Updating MCP versions and checking publication

Roll back Kortix production to a previously released version using existing builds. Covers frontend and backend rollback, database compatibility checks, prevention of unintended frontend rebuilds, and returning to the latest version through a later release.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restore a previous release after a production incident
• Check database compatibility before a rollback
• Prevent frontend rebuilds from overwriting a rollback

Independently review release note drafts against scanned change data. Check factual accuracy, missing items, tone, links, and clear coverage of breaking changes and security updates, then return a verdict with recommended revisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking release notes against scanned changes
• Reviewing breaking change and security notices
• Finding missing links and acknowledgments

Prepare a deployment checklist covering tests, approvals, database changes, release steps, and monitoring. Tailor it to the release and document rollback triggers, the conditions for reverting a change, before production deployment begins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare checks for an upcoming production release
• Review a release with database migrations
• Verify feature flags and CI status before deployment

Prepares a project for open-source release by checking sensitive history, licensing, documentation, tests, and automated publishing. Helps identify gaps so people outside the project can build, use, and contribute to it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a private repository for public release
• Choosing and documenting a project license
• Improving README and contribution instructions

Verify production fixes by connecting code changes and releases to Sentry issues. Compare error events and affected users before and after release, then report whether the fix worked, improved behavior, failed, or lacks enough traffic to judge.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether the release containing a fix appears in Sentry
• Compare error events and affected users before and after release
• Assess improvement, regression, or insufficient traffic

Assesses a release using Sentry errors, recurring problems, affected users, and crash evidence. Compares equivalent periods with the previous stable release, identifies gaps in the evidence, and recommends rollout actions only when the findings support them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing a production release with the previous stable version
• Reviewing new or recurring issues and their user impact
• Checking whether quiet results reflect missing data

Guide npm package releases through dependency checks, version alignment, publishing procedures, and post-release smoke tests, which are basic installation and operation checks. It also documents fallback steps for failed automation and project-specific rules about who initiates releases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check dependencies before publishing to npm
• Align package versions and CHANGELOG entries
• Handle failed release workflows

Build, test, and publish the Windows version of OpenMausBot, including its installer and automatic update files. Check packaged resources and installation behavior, mirror release files for older installations, and investigate users remaining on outdated versions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build and publish a new Windows release
• Investigate installations stuck on an old version
• Check installer behavior and automatic update files

Prepare the Apache Tika website for a release by updating changes, navigation, news, and API documentation. Follow separate workflows for 4.x and 3.x, verify the generated pages, and hand the final commit to a human.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing website updates for a Tika release
• Updating 4.x documentation and API references
• Maintaining versioned documentation for 3.x

Draft huggingface_hub release notes from saved pull request JSON files. The skill groups changes, explains major updates, adds examples from documentation changes, and includes author credits and verified documentation links in a Markdown document.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Drafting release notes from saved pull request data
• Explaining major features and breaking changes
• Adding command or API examples from documentation changes

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when releasing, cutting a release, shipping a new Han version, publishing release notes, or tagging a version. Always stops for approval before creating any tag, because a pushed tag is never moved. Requires the gh CLI, jq, the claude CLI, and a clean git checkout. This is a repository-maintenance skill for the Han repo itself, not a general review or PR skill — use code-review for local review, post-code-review-to-pr to post a PR review, and update-pr-description for PR bodies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release policy for a repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automatically generate user-facing release notes from git commits, pull requests, changelogs, and code changes. Use when preparing software releases, creating version announcements, documenting what changed between versions, or communicating updates to users. Analyzes commit messages, PR descriptions, and code diffs to produce categorized markdown release notes organized by New Features, Improvements, Bug Fixes, and Breaking Changes. Focuses on user-visible changes while filtering out internal/technical details. Triggers when users ask to generate release notes, create changelog, write version announcement, or summarize changes for a release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assists with Morphir CLI release management for finos/morphir, including pre-release verification, extension verification, version bumps, tagging, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live. One step stays a Console action by design and the skill hands it to you: granting the service account release access the first time. Use when uploading or promoting an Android build, wiring a Play service account and fastlane supply lanes, fixing per-versionCode changelogs, raising or halting a staged rollout, or answering what version and fraction production is really serving. NOT FOR: planning or building the app itself (use android-app-factory); live listing and keyword audits (use suede-aso); CI required checks (use suede-ci-gate); iOS release (a private Suede Labs companion, not in this pack: ios-app-store-release).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cut a kolu release — tag master, promote the Unreleased changelog entry, publish a GitHub release. ONLY invoke when the user explicitly types `/release` or `$release`; never auto-select from a natural-language request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Publish a tested Voxt release to the stores: Google Play production, App Store review (iOS + Mac Catalyst), Microsoft Store certification. Use when the user says "promote the release", "publish the apps", "release to the stores", "/promote-release", or after /prepare-release once the staged builds have been tested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.