mysql-domain-delivery

Validate MySQL and MariaDB schema changes for online DDL and replication risk.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill mysql-domain-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mysql-domain-delivery
Source: https://github.com/vTRKA/supervibe/tree/main/skills/mysql-domain-delivery
Command: npx skills add https://github.com/vTRKA/supervibe --skill mysql-domain-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents risky MySQL/MariaDB schema changes by turning unclear migration intent into a production-safe plan with explicit evidence, verification, and rollback discipline.

Core Features & Use Cases

  • Stack-aware MySQL delivery playbook: guides schema design, indexing, and migrations while accounting for InnoDB locking, metadata locks, online DDL behavior, replication lag, and query-plan proof requirements.
  • Online DDL and migration risk control: validates expected DDL algorithms/lock modes (or delegates to gh-ost/pt-osc) and forces compatibility-safe rollout steps such as nullable-first, dual-write/dual-read patterns, and delayed drops.
  • Evidence-first verification and failure handling: requires source-of-truth inspection, scoped commands, and an output/report contract (PASS/PARTIAL/BLOCKED/DEFERRED) that records commands, exit codes, and remaining blockers without guessing.

Quick Start

Ask your AI to plan and verify a MySQL schema/index change using correct InnoDB online DDL assumptions, scoped verification, and a named rollback path.

Frequently Asked Questions about mysql-domain-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely run MySQL schema migrations without locking tables?

Safe MySQL schema migrations require validating online DDL algorithms and lock modes before execution. You must verify InnoDB locking risks and compatibility-safe rollout steps like nullable-first changes to prevent table locks.

What is the best way to plan a rollback for MariaDB indexing changes?

Planning a rollback for MariaDB indexing changes requires establishing a named rollback path before execution. You must define rollback ownership and verify query-plan evidence to ensure changes can be safely reverted.

How does replication lag affect online DDL operations in MySQL?

Replication lag affects online DDL by delaying schema changes across topology nodes. You must assess replication impact and use compatibility-safe patterns like dual-write or delayed drops to prevent deadlock and isolation issues.

When do I need to use dual-write patterns for MySQL column alterations?

You need dual-write patterns for MySQL column alterations when online DDL constraints require compatibility-safe rollout steps. Using dual-write and dual-read patterns prevents locking risks and ensures verification before dropping legacy columns.

Why should I verify query plans before shipping composite index changes?

You must verify query plans before shipping composite index changes because evidence-first scoped validation proves the index resolves intended queries. Without query-plan proof, the schema migration carries unbounded locking and replication risks.

What happens if version or rollback ownership is missing during a MySQL schema deployment?

If version, proof, or rollback ownership is missing during MySQL schema deployment, completion is deferred. The structured delivery report outputs a BLOCKED or DEFERRED status, recording remaining blockers without guessing.