migration
Plan Safe and Reversible Migrations
Complex migrations can lose data or break compatibility during staged rollouts. This skill structures transitions around preservation, verification, rollback, and mixed-version safety.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "migration" from https://skillstore.io/skills/juliusbrussee-migration.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-migration/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「migration」を使用しています。 Migrate customer status from free text to a controlled value set.
期待される結果:
- Expand: add the controlled status field while retaining the original field.
- Migrate: backfill recognized values idempotently and quarantine unknown values.
- Verify: compare counts, unknown values, and read behavior before switching.
- Contract: remove the original field only after rollback is no longer required.
「migration」を使用しています。 Replace API field account_name with display_name during a rolling deployment.
期待される結果:
- Writers temporarily populate both fields.
- Readers accept display_name first and fall back to account_name.
- Telemetry confirms old clients have left the compatibility window.
- Removal requires separate approval after rollback criteria expire.
「migration」を使用しています。 Upgrade a shared authentication dependency across several services.
期待される結果:
- Inventory consumers, supported versions, and authentication behavior before rollout.
- Deploy to a small service cohort with error-rate and login-success checks.
- Pause or roll back when predefined authentication thresholds fail.
- Complete rollout only after every service passes compatibility verification.
セキュリティ監査
安全The skill contains prompt-only guidance for reversible migrations and no executable code. No static or semantic security findings were identified.
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/juliusbrussee-migration/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/juliusbrussee-migration?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/juliusbrussee-migration?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-migration/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/juliusbrussee-migration.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
juliusbrussee. (2026). migration security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-migration/audits/1BibTeX形式の引用
@techreport{juliusbrussee-juliusbrussee-migration-2026,
author = {juliusbrussee},
title = {migration security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/juliusbrussee-migration/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "migration security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "juliusbrussee"
date-released: "2026-08-12"
url: "https://skillstore.io/skills/juliusbrussee-migration/audits/1"
identifiers:
- type: other
value: "skillstore:juliusbrussee-migration:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Evolve a Database Schema
Plan an expand-and-contract schema change that supports old and new application versions.
Transition an API Contract
Stage an API change while preserving existing clients and defining measurable retirement criteria.
Upgrade a Critical Dependency
Design a reversible dependency upgrade with compatibility checks, staged rollout, and rollback triggers.
これらのプロンプトを試す
Plan this migration: [change]. Include prerequisites, forward steps, verification, and rollback.
Plan [change] while versions [old] and [new] run together. Identify compatibility risks, mitigations, and exit criteria.
Design expand, migrate, verify, and contract stages for [change]. Define invariants, idempotent retries, observability, and rollback boundaries.
Analyze [architecture and change]. Map readers, writers, ownership, failure modes, tests, rollback triggers, and evidence required before each stage.
ベストプラクティス
- Document readers, writers, owners, invariants, and compatibility windows before changing production behavior.
- Use idempotent steps with observable checkpoints and explicit rollback triggers.
- Authorize destructive contraction separately after preservation and compatibility evidence passes.
回避
- Do not combine expansion, migration, and destructive cleanup into one irreversible release.
- Do not assume all services, clients, or workers update simultaneously.
- Do not treat deployment success as proof of data preservation or behavioral compatibility.
よくある質問
What migration types does this skill support?
Does this skill run migration commands?
How does it support rollback?
Can it plan rolling deployments?
What information should I provide?
When should contraction begin?
開発者情報
作成者
juliusbrusseeライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
ad241fa81de50eaaf50f69dc3681d60cafdddb21
メンテナンスの新しさ
2026/8/13
利用状況
0 ダウンロード · 0 閲覧
ファイル構成