'eas' 검색 결과

Create and edit EAS workflow YAML files to automate builds and deployments for Expo projects. Check required settings, job dependencies, and dynamic values against the latest schema, which defines the accepted configuration.

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

• Create an automated build workflow for an Expo project
• Edit EAS deployment automation
• Check workflow settings and job dependencies

Build beta versions of the Composio CLI, promote a tested beta to a stable release, and investigate failed releases. Guides verification of published binaries and installation tests through the Build CLI Binaries workflow.

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

• Build a CLI beta release
• Promote a tested beta to stable
• Verify release assets and installation

Prepare a Symphony release by updating its version, running checks, merging the change, and tagging the merged commit. Then monitor the Burrito release workflow and verify that the GitHub release contains the expected assets.

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

• Release a specified Symphony version
• Prepare the next patch release
• Tag the merged release commit

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.

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

• Prepare a release candidate and checklist
• Collect testing and release readiness results
• Decide whether a release should proceed

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.

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

• Prepare an OpenSEO release pull request
• Summarize changes since the previous release
• Update the version and release notes together

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.

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

• Publishing a patch, minor, or major OpenWork release
• Reviewing open fixes before creating a release tag
• Recovering distribution steps for an existing release tag

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.

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

• Checking a newly published release
• Reproducing a bug in a released version
• Verifying a hotfix after updating a release tag

Expo (EAS) iOS/Android アプリのデプロイ自動化スキル。 App ID 登録、証明書・プロビジョニングプロファイル作成、 EAS ビルド、TestFlight 配布、App Store 提出までを CLI から実行する。 任意の Expo プロジェクトで使える汎用スキル。 Use when: App ID を登録したい、証明書を作りたい、Bundle ID を設定したい、 EAS でビルドしたい、TestFlight に配布したい、App Store に提出したい。 Triggers: "App ID", "Bundle ID", "証明書", "certificate", "provisioning", "プロビジョニング", "eas credentials", "eas build", "eas submit", "TestFlight", "App Store 提出", "署名", "signing"

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

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).

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

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.

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

• Delegating a coding task through release
• Connecting a ready PR merge to release work
• Running build and release in sequence

Send proofs, planning questions, or difficult debugging tasks to DeepSeek's reasoning model. Receive the final answer and model-provided reasoning text in separate fields, with token usage reported for reviewing responses and costs.

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

• Requesting a mathematical proof
• Planning work that requires several reasoning steps
• Investigating root causes of difficult bugs

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.

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

• Add the latest missing release entry
• Align changelog text with GitHub Releases
• Summarize changes between release tags

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

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.

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

• Preparing a new Worktrunk release
• Writing release notes from code changes
• Reviewing data-loss risks before release

Prepare a software release by analyzing code changes, writing English and Chinese release notes, updating versions with changeset, and creating commits and a release pull request for review before automated publishing.

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

• Preparing a patch release after bug fixes
• Writing English and Chinese release notes
• Creating a release pull request for a protected main branch

Prepare a release recap from changes merged since the last release tag. Group work by author, count features, bug fixes, and maintenance tasks, and post the reviewed summary to Slack for final quality checks.

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

• Prepare a change recap for pre-release quality checks
• Review changes included in an already-tagged pre-release
• Share release changes grouped by author on Slack

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 공지를 작성합니다. 버전별 업데이트 절차와 사용자 테스트 항목을 정리하고 승인 후 게시도 지원합니다.

• beta 버전 공지를 작성할 때
• stable 버전 업데이트 방법을 안내할 때
• 사용자 테스트 항목을 정리할 때

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

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.

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

• Draft release notes from scan results
• Organize features, fixes, breaking changes, and security updates
• Prepare Markdown for a CHANGELOG or GitHub release

Guides Apache OpenDAL release managers through preparation, release candidates, verification, voting, and publication. It tracks the current stage, checks external systems, and distinguishes core, candidate, and package versions when deciding the next release action.

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

• Preparing a weekly candidate or manual release candidate
• Checking release CI and staged source artifacts
• Preparing a vote and verifying its outcome

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".

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

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.

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