eightforge-migration-reviewer

Reviews Supabase and Postgres schema migrations for rollout safety, backfills, and rollback.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-migration-reviewer-ericanalysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eightforge-migration-reviewer
Source: https://github.com/EricAnalysis/eightforge-os/tree/main/.cursor/skills/eightforge-migration-reviewer
Command: npx skills add https://github.com/EricAnalysis/eightforge-os --skill eightforge-migration-reviewer-ericanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Database migrations in production risk corrupting authoritative records, breaking tenant isolation, or losing data during rollback. This Skill reviews EightForge schema and data migrations against a strict checklist covering ordered rollout, measured backfills, RLS alignment, compatibility windows, and zero-downtime safety. ## Core Features & Use Cases - Rollout Phase Review: Verifies the explicit expand -> backfill -> validate -> cutover -> contract state machine with entry/exit gates, owners, and compatibility windows. - Backfill and Rollback Validation: Checks that backfills are deterministic, idempotent, and measured with source/target counts, and that rollback accounts for writes accepted after deployment. - Authority and Tenant Safety: Classifies every affected table as production authority, compatibility, shadow, design target, or superseded, and confirms organization/project scoping and RLS behavior are preserved. - Use Case: Before merging a Supabase migration that adds an index and backfills a new column, run this review to confirm the index strategy, backfill idempotency, mixed-version safety, and contraction plan are sound. ## Quick Start Review the pending Supabase migration in supabase/migrations for rollout ordering, backfill safety, RLS impact, and rollback risk.

Frequently Asked Questions about eightforge-migration-reviewer

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

FAQPage Schema
How do I review a database migration before deploying to production?▼

Review the migration against an explicit rollout state machine: expand, backfill, validate, cutover, contract. Confirm backfills are idempotent with measured counts, rollback handles writes accepted after deployment, and constraints, indexes, and RLS policies are safe for existing and concurrent data.

How to run zero-downtime schema migrations in Postgres?▼

Use an expand-then-contract pattern: add new schema alongside the old, backfill with deterministic idempotent jobs, validate with measured counts, cut over readers, then contract only after inventorying all compatibility readers, writers, jobs, and stale application versions.

Does this migration review work with Supabase and RLS policies?▼

Yes, it covers Supabase and Postgres migrations including RLS policy changes, checking that organization and project scoping is preserved. Runtime RLS and query safety findings are routed to the paired Supabase reviewer while this review owns migration-time RLS sequencing.

What makes a database backfill safe to run in production?▼

A safe backfill is deterministic, idempotent, and scoped, with measured source and target counts, invariants, gap and reject handling, and duplicate handling. It must not rewrite immutable historical records and needs rerun evidence before being declared complete.

When should a shadow schema be promoted to production authority?▼

Promotion requires a recorded cutover decision, verified production readers, disposition of compatibility readers, and evidence the promoted path satisfies its authority gates. A deployed shadow schema with populated rows remains shadow implemented until that cutover is recorded.