Skip to content
cccskills
FreePublished on GitHub

data-contract-migrations

Design and verify data contracts, schema changes, migrations, rollbacks, backfills, compatibility windows, tenant isolation, and API-to-database field mapping. Use when changing database schema, event payloads, persisted documents, analytics tables, multi-tenant data boundaries, or any user-visible data contract where silent fallback or undeclared fields would be dangerous.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook
See how to install

Files included (2)

  • SKILL.md2.4 KB
  • agents/openai.yaml256 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Data Contract Migrations

Purpose

Use this skill when data shape changes can break reads, writes, reports, tenants, or integrations. The goal is an explicit compatibility and migration plan, not just a SQL diff.

Preflight

Gather these facts before proposing changes:

  1. Current schema, models, serializers, API contracts, and persisted samples.
  2. Writers and readers of each field.
  3. Migration tool and rollback support.
  4. Data volume, tenant boundaries, and backfill cost.
  5. Required zero-downtime or maintenance-window constraints.
  6. Existing tests or fixtures that prove compatibility.

If the current data does not contain a field, treat it as absent. Do not invent fallback fields.

Migration Design

Use expand-migrate-contract for production systems:

  1. Expand: add nullable columns, new tables, new enum values, or versioned payloads without breaking old readers.
  2. Dual-write or adapter: write both old and new forms when needed.
  3. Backfill: migrate historical data with batching, checkpoints, and retry behavior.
  4. Read switch: move readers to the new contract after verification.
  5. Contract: remove old fields only after the compatibility window and rollback risk pass.

For small systems, a direct migration is acceptable only when downtime, rollback, and data loss risks are explicitly low.

Required Checks

Every plan must include:

  • Forward migration command.
  • Rollback or roll-forward recovery command.
  • Backfill idempotency and resume behavior.
  • Data validation query before and after.
  • Tenant isolation check when tenants exist.
  • API/serializer compatibility test.
  • Observability for migration progress and failure.

Output Shape

contract_change:
affected_readers_writers:
migration_strategy:
backfill_plan:
rollback_or_recovery:
tenant_and_security_checks:
verification_queries:
test_commands:
release_gate:

Raise errors for missing critical data rather than warning and falling back to incomplete output.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agentsmd-optimize

Free

Audit and organize AI coding-agent instructions, including AGENTS.md, CLAUDE.md, skills, and agent definitions. Use when the user asks to diagnose conflicting instructions, excessive approval pauses, broad skill triggers, duplicate guidance, or broken instruction references, or to clean up that instruction set. Ordinary code review, Markdown editing, or application debugging alone does not trigger this workflow. Inspection stays read-only; apply changes when authorized.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

agentsmd-scaffold

Free

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

api-design

Free

REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

app-ui-design

Free

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

app-user-story-qa

Free

End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

architecture-foundation

Free

Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.

The English summary is being prepared. Showing the original description.

majiayu000/spellbook288Updated Oct 20, 2026

See all skills by majiayu000

Report a problem with this skill