「rollback」の検索結果

Change a Mac's main display resolution in one command: real pixels instead of 4K HiDPI so remote desktop (AnyDesk), screen recording and Screenpipe stop lagging. Use when a remote session is slow or a lower or original resolution is needed: lists modes, picks by width, height, pixel width and refresh rate, self-tests five known traps, verifies after the change and prints a one-line rollback. Triggers: /display-mode, lower the resolution, set 1920x1080, AnyDesk is slow, restore resolution.

日本語の概要は準備中です。原文の説明を表示しています。

Operational safety for deployless repositories. Use after mainline deployment and runtime release controls are designed, when a repo needs traces, replay tests, observability, rollback drills, smoke checks, compatibility windows, or expand-contract migration safety.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "plan my launch tier", "how big should this launch be", or "build a launch risk register with kill criteria"; produces a tier decision (Tier 1 flagship all-channel / Tier 2 targeted / Tier 3 changelog-level), a launch-type declaration (new-product / feature / relaunch / partnership with co-marketing split), an effort calibration matrix (tier to channel intensity and asset scope), D0/W1/M1 KPI targets (labeled Estimated), a risk register (likelihood x blast-radius, owners, mitigations, kill criteria / rollback thresholds), and a T-8w to T+4w timeline skeleton. Not for picking the launch date or window — use launch-window-planner; not for creator-channel launch campaigns — use campaign-planner. 发布分级/发布类型/风险登记册/kill criteria

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "read back" a paid campaign change, "did this ad change work", or "compare ROAS/CPA before and after"; reads ROAS/CPA against a control over a fixed readback window and returns a Promote / Keep-testing / Rollback / Unproven readback decision with the math delegated to roi-calculator. Not for RQS scoring or veto adjudication — use ad-account-auditor; not for the ROI ratio math — use roi-calculator; not for cross-channel rollups — use performance-analyzer. 付费广告复盘/ROAS回看/投放效果归因

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar early-warning (Estimated heuristic), PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds against the launch-tier KPI targets. Not for launch-day go/rollback calls — use launch-day-conductor; not for metric deep-dives — use performance-analyzer; not for SEO rank tracking — use rank-tracker. 发布监控/排名轮询/火焰战比/spike-sustain

日本語の概要は準備中です。原文の説明を表示しています。

Execute database migrations across ORMs and platforms with zero-downtime strategies, data transformation, and rollback procedures. Use when migrating databases, changing schemas, performing data transformations, or implementing zero-downtime deployment strategies.

日本語の概要は準備中です。原文の説明を表示しています。

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

日本語の概要は準備中です。原文の説明を表示しています。

Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Cloudformation Deep — aWS CloudFormation deep stack management. Covers stack operations, change sets, drift detection, nested stacks, stack sets, resource imports, template analysis, and rollback troubleshooting. Use when managing complex CloudFormation deployments, debugging stack failures, detecting drift, operating stack sets, or analyzing template dependencies.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Codedeploy — aWS CodeDeploy application and deployment management. Covers applications, deployment groups, deployment history, deployment configurations, instance health, target revisions, and rollback settings. Use when inspecting deployments, debugging failed deployments, reviewing deployment strategies, or auditing deployment group configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Appconfig — aWS AppConfig configuration management and deployment analysis. Covers applications, environments, configuration profiles, deployment strategies, hosted configurations, and deployment status monitoring. Use when inspecting AppConfig deployments, reviewing feature flags, auditing configuration profiles, or debugging deployment rollbacks.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Argocd — argoCD GitOps continuous delivery management for Kubernetes. Covers application sync status, deployment health, rollback operations, repository management, cluster registration, RBAC analysis, and application diff review. Use when checking deployment status, investigating sync failures, managing GitOps applications, or auditing ArgoCD configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when modifying OpenAmer's own core code safely. Gate every change behind the test suite with automatic rollback.

日本語の概要は準備中です。原文の説明を表示しています。

Database migration v3 — Flyway, Liquibase, zero-downtime, rollback, schema evolution, data migration

日本語の概要は準備中です。原文の説明を表示しています。

BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.

日本語の概要は準備中です。原文の説明を表示しています。

Solution architect that creates implementation blueprints before building. Maps 2-3 approaches ranked by simplicity, creates phased build plans with rollback points, and checks dependencies. Use when you need to design a solution, create a blueprint, plan before building, or take a task from the audit and need an implementation plan. Part of the architect-system loop. Reads from system/audit-report.md. Outputs to system/blueprints/.

日本語の概要は準備中です。原文の説明を表示しています。

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

日本語の概要は準備中です。原文の説明を表示しています。

アプリやコードが壊れたとき、被害を広げずに安全な状態へ戻すための復旧ワークフロー。「壊れた」「動かなくなった」「エラーが出るようになった」「元に戻したい」「前の状態に戻して」「デプロイしたらおかしくなった」「昨日まで動いてた」といった訴えがあったら、原因調査や修正を始める前にまずこのスキルを使うこと。特にエンジニアが常駐しないチームでは、ユーザーがパニック状態で曖昧な依頼をしてくることが多いので、破壊的な回復手段（git reset --hard, git clean, force push等）に飛びつかず、このスキルの手順で退避→切り分け→安全な復旧を行う。

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the aoa-safe-infra-change workflow inside an abyss-* repository using repo-relative operational surfaces, explicit local authority notes, rollback posture, and local validation commands. Use when the base infra-change workflow is correct but a thin project overlay is needed for one abyss repo. Do not use when the base skill is sufficient without local adaptation or when the task is really about producing a shareable artifact.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure data model/DB designs cover constraints, integrity, indexes, migrations, rollback, and operational impacts.

日本語の概要は準備中です。原文の説明を表示しています。

スキーマ/データ移行の安全性を framework 非依存で審査する。破壊的スキーマ変更・ロック誘発・backfill・ロールバック可逆性・expand-contract の段階適用を、prisma / typeorm / Rails / Django / Alembic / 生 SQL などに横断適用する。

Ensure cross-service integration defines contracts, ownership, failure handling, versioning, and rollout/rollback expectations.

日本語の概要は準備中です。原文の説明を表示しています。

Audit required bioinformatics command-line tools against Lmod or Environment Modules on Linux HPC clusters, resolve executable and version requirements, and reproducibly deploy missing software through a site-approved EasyBuild, Spack, Bioconda/micromamba, Apptainer, binary, or source-build workflow. Use when Codex must inspect module availability, diagnose a missing or wrong-version bioinformatics tool, install scientific software on Slurm/PBS clusters, publish or validate modulefiles, or produce an auditable and rollback-ready cluster software deployment.

日本語の概要は準備中です。原文の説明を表示しています。