'dry-run' 검색 결과

Prepare a Cherry Studio release by checking changes against the published version, writing English and Chinese release notes, updating version metadata, and creating a release branch after review to start the build workflow.

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

• Preparing a patch, minor, or major release
• Preparing a beta or release candidate
• Writing release notes from final user-visible changes

Dry-run one cycle of a sales agent workflow without calling language models. Validate the template and agent types, check budget reservations, generate agent prompts, and record a structured status summary for downstream automation.

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

• Demonstrating one cycle of a sales agent workflow
• Checking template validity and agent types
• Verifying budget caps and reservations

Back up and restore OmniRoute data from the command line. Manage incremental snapshots, scheduled backups, encryption, and cloud synchronization, with options to compare differences and preview data transfers or imports before applying them.

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

• Create a backup before restoring data
• Schedule recurring backups
• Compare differences before cloud synchronization

Fill Japan Post Web Yu-pri contents forms from JSON or CSV files through the browser. Preview planned entries, inspect page status, and save screenshots to support repetitive item entry before final shipment confirmation.

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

• Entering multiple contents lines from JSON or CSV
• Previewing item entries before filling the form
• Saving screenshots and checking page status

Prepare and launch nf-core/pacsomatic workflows for matched tumor and normal PacBio HiFi samples. Generate sample sheets and launch files from unaligned BAM inputs, run local checks, submit cluster launchers, and troubleshoot startup failures.

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

• Prepare sample sheets for matched tumor and normal samples
• Review generated launch files with a dry run
• Submit a Nextflow launcher to a computing cluster

Review open Mastra GitHub issues and trace reported defects to source code. Apply the @mastra/core label to confirmed core bugs, report uncertain ownership, and summarize whether fixes are active, stale, or unclaimed.

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

• Checking whether reported bugs belong to @mastra/core
• Labeling confirmed core bugs with supporting evidence
• Previewing issue classifications without changing GitHub

Build a game launch checklist covering code, content, quality, stores, legal preparation, infrastructure, marketing, and operations. Tailor checks to the project's stage and release requirements, then summarize blockers, accepted risks, missing confirmations, and required sign-offs.

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

• Reviewing launch readiness across departments
• Preparing checks for itch.io, Steam, or console releases
• Separating launch blockers from unassessed items

Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.

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

• Preparing a new version from recent changes
• Updating changelogs in multiple languages
• Previewing release changes without modifying files

Import existing notes and agent instructions into LifeOS by splitting content into sections and proposing destinations. Review uncertain classifications, approve selected groups, and retain source information alongside the imported material.

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

• Importing Obsidian or Notion exports into LifeOS
• Moving notes from an older LifeOS installation
• Reviewing and importing CLAUDE.md or Cursor rules

Validate a KrillinAI production plan combining subtitles, dubbing, landscape or portrait videos, and covers. The skill explains how to run stages separately, verify their files, and resume failed work using existing outputs.

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

• Validate a plan with several media outputs
• Map requested outputs to individual commands
• Resume a failed stage using existing files

Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.

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

CloudBase declarative deployment from a cloudbaserc config (声明式部署, 配置式部署, cloudbaserc 部署) through the deployBuild / deployPlan / deployApply MCP tools. Use when deploying database, functions, app, hosting, or gateway resources described in cloudbaserc.json/yaml as a single desired-state config, when a user wants to build static hosting artifacts locally first (deployBuild), or wants a dry-run plan before applying (deployPlan), or when handling multi-environment deploys via mode / envOverrides. Covers build-plan-apply flow (deployBuild local build → deployPlan dry-run → deployApply confirm=true), hosting build-output neutralization, envId resolution priority, only/skip filtering, concurrency, and continueOnError. Prefer deployBuild (when hosting declares a buildCommand) and deployPlan before deployApply; do not confuse with per-resource tcb CLI deploy or single-function deploy.

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

Power Platform のテナント / 環境ガバナンスを確認・設定する管理スキル。開発着手前の環境チェック（既定環境ではないか・マネージド環境・Dataverse / Code Apps / MCP の有効化・セキュリティ ロール・管理 API アクセス）と DLP 事前チェックを非対話スクリプトで実行し、必要ならマネージド環境設定・カスタムコネクタの DLP 分類・ACP（Advanced connector policies）の許可コネクタを dry-run 付きで変更する。Microsoft 第一者サービスだけを許可する ACP 推奨プロファイルの適用と、クラシック DLP から ACP への移行も支援する。クラシック DLP と ACP は既定の混成モードで併用され、より制限の厳しい方が適用されるため両方を確認する。オプションとして、既定環境 / 個人開発者環境 / 市民開発者環境 / AI CoE セントラル / AI CoE 内製開発の 5 グループからなるテナント全体の環境戦略を、読み取り専用スキャン → 移行プラン（admin-migration-plan.md）→ レビュー → 適用の順で策定・実行する。設定は環境グループのルールで行うのを原則とし、グループ ルールに無い項目（既定環境ルーティング・Dataverse for Teams 禁止・Dataverse 検索・グループへの割り当て・Copilot クレジット配分）だけをテナント設定・環境個別設定・Dataverse の組織設定で補う。IP 制限・テナント分離・監査ログ・ライセンス配分などの管理設定は references にまとめる。

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

Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: 'bulk update N issues', 'mass transition', 'transition 50+ issues to Done', 'bulk-clone', 'bulk-delete'. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).

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

Bulk Confluence operations on 10+ pages via the confluence-as wrapper: bulk-label / bulk-move / bulk-delete. Dry-run is MANDATORY first. Triggers: 'bulk update N pages', 'mass label', 'delete all pages matching CQL', 'bulk-move pages to PARENT'. NOT for single-page ops (mk:confluence-page); NOT for comment/attachment ops (mk:confluence-collaborate).

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

Prefab / Scene / Asset を壊さず編集する。preflight 診断 → dry-run 差分 → confirm + change_reason 監査 → runtime 検証の 4 段ゲートを 1 経路で踏む。 トリガー: パッチ適用、Prefab Variant 編集、`set_property` / `patch_apply` / `revert_overrides` を伴う変更全般。

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

Unity Prefab / Scene / Asset の壊れた参照・Variant override・配線ミスを構造化応答で診断し、 dry-run → confirm 経路で安全に修復するための MCP ツールリファレンス。 Editor Bridge のセットアップ手順もここに含む。 トリガー: .prefab, .unity, .asset, .mat, Prefab, Variant, 配線, 参照, 壊れた参照, broken reference, GUID, fileID, override, パッチ, patch plan, validate refs, validate structure, where-used, inspect variant, inspect wiring, inspect hierarchy, wiring, null参照, null reference, MonoBehaviour, 階層, hierarchy, Transform整合, 孤立, orphan, 重複fileID, duplicate fileID, Editor Bridge, Bridge セットアップ, bridge setup, deploy_bridge, UNITYTOOL_BRIDGE_WATCH_DIR, watch ディレクトリ のいずれかに該当する作業で使用する。

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

governance artifactのmigration候補とdry-run差分を確認したいとき、rollback条件を保った移行を実行したいときに使う。

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

How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers). Covers the scout SKILL.md anatomy, the emit contract, the dedupe + scratchpad-memory conventions, the per-team skills-store path vs the canonical in-repo path, and the emit-and-inspect test loop (with dry-run as an optional safety net). Trigger on "write/edit/customize a signals scout", "new scout for X", "tune my scout schedule", "make a scout that watches <event>".

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

Google Workspace CLI (gws) リファレンス。Rust 製。 `gws <service> <resource> <method>` 形式で Gmail / Drive / Calendar / Sheets / Docs / Chat 等 19 サービスを統一操作。Google Discovery Service 経由の動的コマンド生成。 `+` プレフィックスのヘルパーコマンド（+send, +agenda, +upload, +triage 等）、 ワークフロー合成（+standup-report, +meeting-prep, +weekly-digest）、 OAuth / サービスアカウント / CI ヘッドレス認証、env vars / .env / keyring 設定、 グローバルフラグ（--dry-run, --page-all, --sanitize）、exit codes、Model Armor 統合。

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

cc-sdd実装用統合ブランチのコミット群（ベースブランチとの差分）をreview slice単位のstacked PRに再構成する際に使用。「review sliceに分割」「stacked PRを作成」「PRをスタックして」「レビュー用にPRを分けて」「review slice stack」という依頼でトリガーする。dry-run（既定）でslice計画を提示し、apply指示で実際にブランチ・PRを作成する。

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

Author and run unattended autonomous workflows — "workflow", "unattended", "run on a schedule", "automate this overnight", "set up an autonomous", "dry-run". Mandatory budget guards, a separate verification gate, idempotency, and dry-run on by default.

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

macOS의 Things 3에서 오늘의 할 일과 수신함을 확인하고 작업을 추가, 검색, 수정합니다. 메모, 마감일, 태그, 체크리스트도 다룹니다.

• 오늘의 할 일과 수신함 확인
• 마감일과 체크리스트가 있는 작업 등록
• 기존 작업 검색과 수정

질문과 선택한 파일을 다른 AI 모델에 전달해 코드 검토, 오류 조사, 설계 조언을 받습니다. 실행 전에 전송 내용과 토큰 사용량을 확인할 수 있습니다.

• 코드에 대한 다른 AI의 의견 확인
• 관련 파일을 첨부해 오류 조사
• 설계 및 리팩터링 방안 비교