'eas' 검색 결과

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.

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

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.

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

Tested reasoning approaches for Claude prompts — 18 variants across 6 categories (Analytical, Strategic, Creative, Technical, Research, Comparative). Use when the user wants a specific reasoning template — retrieving, reviewing, customizing, or combining reasoning instructions for a prompt. Trigger on: "give me the Root Cause Diagnosis approach," "show me the reasoning template for," "I need the Evidence Synthesis method," "show me analytical reasoning options," "combine reasoning approaches for," "show me all reasoning variants." Also use when a prompt produces shallow output and the fix is a reasoning upgrade. Provides 18 tested approaches for analytical, strategic, creative, technical, research, and comparison tasks. If the user is unsure which reasoning method fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts — use rootnode-prompt-validation if available. Do NOT use for project-level audits — use rootnode-project-audit if available.

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

Paperclip 안정 버전의 변경 기록을 바탕으로 dotta의 대화체를 따른 Discord 공지를 작성합니다. 주요 변경과 향후 계획을 정리해 사람이 복사하여 게시할 초안을 저장합니다.

• 안정 버전의 Discord 공지를 작성합니다
• 새 버전이나 날짜에 맞춰 공지를 갱신합니다
• 주요 변경과 향후 계획을 정리합니다

GitHub 소프트웨어 출시의 버전 제안과 변경 기록 작성부터 테스트, 빌드, 단계적 배포까지 연결합니다. 문제 발생 시 이전 상태로 되돌리는 롤백도 다룹니다.

• 버전 업데이트와 출시 문서 준비
• 여러 패키지와 저장소 동시 출시
• 모니터링과 롤백을 포함한 단계적 배포

여러 AI 에이전트가 GitHub 소프트웨어 출시를 진행하도록 돕습니다. 버전 갱신, 변경 이력, 테스트, 여러 환경 배포와 문제 발생 시 롤백을 다룹니다.

• 버전 갱신과 출시 문서를 준비합니다
• 여러 패키지의 출시를 조율합니다
• 출시 전 테스트와 안전성을 확인합니다

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

Prepare an AionUi release by checking AionCore assets, updating versions, and generating a changelog. Run quality checks, create a pull request with automatic merging enabled, then tag the merged release to trigger its build.

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

• Releasing the next AionUi patch version
• Releasing with explicitly chosen UI and Core versions
• Preparing a frontend-only release

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

Generate improvement ideas for an existing product from product management, design, and engineering perspectives. Produce five ideas per perspective, then select the top five based on goals, potential impact, feasibility, and differentiation, with reasons and assumptions to test.

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

• Brainstorming features for an existing product
• Exploring solutions to a customer problem
• Comparing ideas from three professional perspectives

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

Prepare and deploy Expo apps to iOS and Android stores or the web using EAS, Expo's build and deployment services. Covers production builds, store submissions, beta distribution, preview deployments, and automated release workflows.

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

• Prepare Expo apps for iOS and Android store submission
• Distribute an iOS beta through TestFlight
• Deploy a web app and create a PR preview

Guide an app release through version updates, merging, Git tags that mark a release version, and publication checks. Follow the specified package update commands and rerun the release workflow when a tag needs another attempt.

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

• Updating versions across app packages
• Triggering a release with a Git tag
• Rerunning the release workflow

Turn Git commits and pull request details into release notes in three formats: a changelog section, a release PR description, and a user announcement. Group changes, explain user impact, and flag database migrations.

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

• Prepare a changelog for a release
• Draft a release pull request description
• Explain updates to users in plain language

Validate a Kiln release candidate with standard code checks and selected tests against live APIs. Diagnose failures, inspect outdated model selections and coverage gaps, and produce a report with recommended actions without changing code or tests.

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

• Validate a release candidate before publication
• Diagnose failures in live API tests
• Check test model selections for outdated versions

Draft release notes that explain what changes for users. Verify the release range, reconcile commits and reversals, and highlight breaking changes, migration steps, and relevant pull requests with evidence.

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

• Drafting release notes for a specific version
• Explaining breaking changes and migration steps
• Summarizing user-visible changes across pull requests

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

Prepare and deploy Expo apps to iOS and Android stores or the web using EAS, Expo's build and deployment services. Covers production builds, store submissions, beta distribution, preview deployments, and automated release workflows.

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

• Prepare Expo apps for iOS and Android store submission
• Distribute an iOS beta through TestFlight
• Deploy a web app and create a PR preview

Check published EAS Updates from the command line using crash rates, user counts, and payload size. Compare adoption of the app's bundled version and over-the-air updates, with JSON output for automated health checks.

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

• Check update health after publishing
• Compare crash rates with a previous release
• Compare bundled and over-the-air update adoption

Turn git history since a release tag or specified reference into clear App Store release notes. Identify user-visible changes, remove duplicates and internal maintenance work, and draft concise bullets that explain what changed for users.

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

• Draft App Store What’s New text
• Summarize changes since the last release tag
• Create release notes for a specified commit range

Review a JavaScript SDK release plan or final candidate against the previous release. Check compatibility, packaging, regressions, and Changesets version records, then recommend shipping or blocking with supporting evidence and a separate assessment of documentation coverage.

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

• Review the next SDK release plan
• Assess whether a final release candidate can ship
• Check generated versions and changelogs for consistency

Apply NOWAIT to shorten reasoning model outputs by suppressing reflection words during generation. Includes integration examples for HuggingFace Transformers and vLLM, with guidance on model suitability and potential accuracy loss in distilled models.

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

• Reducing tokens used in lengthy reasoning
• Introducing NOWAIT into model inference
• Checking model suitability and accuracy risks

[omh] Releasing an iOS or Android app through the stores -- signing, the privacy manifest, a TestFlight or Play beta, a staged rollout, a hotfix: prepare each gate the store enforces, and plan the halt and the next build before the rollout starts, because a store release cannot be rolled back. Use when the user says: mobile-release, mobile release, mobile app release, ios release, android release, app store release, app store submission, submit to the app store.

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