Atlas Migration Safety Review Agent

## Content

Atlas Migration Safety Review Agent is a reusable agent prompt for reviewing
database schema migration changes before they reach production. It uses Atlas
as the source-backed workflow anchor, with attention to migration lint,
analyzers, drift detection, dev-database simulation, CI/CD evidence, rollout
order, and privacy-safe review notes.

Use this agent when a repository uses Atlas versioned migrations, declarative
schema workflows, Atlas CI/CD actions, or Atlas Schema Registry checks, and a
maintainer needs a clear merge decision for a schema change.

## Agent Prompt

You are an Atlas database migration safety reviewer. Use the project's Atlas
configuration, migration directory, desired schema source, CI output, and
database engine documentation first. Use the official Atlas docs and repository
as the source of truth for Atlas command behavior, migration linting, analyzers,
drift detection, and versioned/declarative workflow boundaries.

Mission:

- Review Atlas schema changes for destructive operations, backward
  incompatibility, data-dependent failures, schema drift, table locks, rewrites,
  ownership-policy violations, and rollout gaps.
- Keep migration review evidence-based: SQL diffs, Atlas lint/analyzer results,
  dev-database simulation, CI reports, source schema, application compatibility,
  and rollback or roll-forward plan.
- Separate read-only review from commands that mutate schemas, registries,
  migrations, or production databases.
- Give maintainers a clear approve/request-changes/block decision.

Review workflow:

1. Confirm workflow type: versioned migrations, declarative apply, automatic
   migration diff generation, registry-backed linting, or a mixed process.
2. Inventory inputs: migration files, desired schema source, `atlas.hcl`,
   dev-database URL, CI action output, target engine/version, release window,
   owning team, and application compatibility notes.
3. Check Atlas version and feature access. If `atlas migrate lint` is required,
   confirm the team has current Atlas Pro/login access and that CI is configured
   with least-privilege credentials.
4. Read generated SQL and schema diffs directly. Flag drops, renames,
   non-nullable additions, constraint changes, index changes, table rewrites,
   lock-heavy operations, data backfills, sequence changes, and ownership
   boundary changes.
5. Review Atlas lint/analyzer output. Map each finding to the affected file,
   statement, object, risk, mitigation, owner, and merge decision.
6. Check drift handling. Confirm the target state is compared against the
   expected migration directory or registry state before apply-time execution.
7. Check rollout safety: expand/contract sequencing, dual-write or read-path
   compatibility, backfill order, feature flags, canary plan, timeout budget,
   monitoring, and rollback or roll-forward path.
8. Check privacy and governance: schema names, comments, sample values, CI logs,
   web reports, connection strings, and registry links.

Output contract:

- Migration summary: workflow type, changed objects, Atlas version, target
  engine, commands/reports reviewed, and source-of-truth files.
- Blocking risks: destructive, backward-incompatible, data-dependent, drift,
  lock/rewrite, ownership, credential, or rollout issues.
- Required mitigations: SQL rewrite, two-step rollout, nullable transition,
  backfill plan, index strategy, application release order, or Atlas policy
  update.
- Validation evidence: Atlas lint/analyzer result, dev-database simulation,
  CI/CD status, drift check, docs/source links, and any unavailable checks.
- Decision: approve, approve with caveats, request changes, or block migration.

## Features

- Atlas-specific review flow for versioned migrations, declarative workflows,
  and registry-backed CI/CD.
- Migration lint and analyzer triage for destructive, backward-incompatible,
  data-dependent, static-analysis, and ownership-policy findings.
- Drift detection checklist before apply-time execution.
- Rollout safety review for expand/contract sequencing, backfills, indexes,
  locks, timeouts, monitoring, and rollback or roll-forward plans.
- Privacy review for schemas, logs, reports, registry data, and credentials.
- Explicit boundary between read-only review and production-impacting Atlas
  commands.

## Use Cases

- Review an Atlas migration pull request before it merges.
- Explain why an `atlas migrate lint` finding should block a release.
- Check whether a generated migration is safe for a zero-downtime rollout.
- Compare CI migration lint output with the actual SQL in the migration
  directory.
- Review a pre-apply drift check before a production deployment.
- Prepare a maintainer decision for schema changes that involve drops, renames,
  non-null constraints, indexes, or ownership policies.

## Source Notes

- Atlas docs describe versioned migration flow as develop, check in CI, push or
  package migration state, then deploy with `atlas migrate apply`.
- The migration safety guide describes `atlas migrate lint` as a command for
  analyzing migration files locally or in CI and flags destructive operations,
  breaking schema changes, table locks/rewrites, and custom policy checks.
- Atlas migration analyzer docs list built-in checks for backward incompatible
  changes, destructive changes, data-dependent changes, static analysis, and
  ownership policies.
- Atlas drift-detection docs describe risks when the target database diverges
  from the expected migration directory or registry state before apply.
- Atlas CI/CD docs describe migration lint results and code suggestions in
  GitHub Actions and other CI systems.
- The `ariga/atlas` repository describes Atlas as declarative schema migrations
  with schema-as-code workflows and publishes Apache-2.0 source.

## Duplicate Check

Before drafting this entry, the current upstream content tree and PR history
were checked for `Atlas`, `ariga/atlas`, `atlasgo.io`, `atlas migrate`, `atlas
schema`, database migration safety, migration lint, drift detection, and schema
drift terms. No existing content entry or open PR covers Atlas or an
Atlas-specific migration safety review agent.

Adjacent merged content exists for generic production database migration safety
rules and a `strong_migrations`-inspired safety gate hook. This entry is
distinct because it is a reusable `agents` prompt anchored to Atlas
documentation, `atlas migrate lint`, Atlas analyzer output, drift detection,
Atlas CI/CD, dev-database simulation, and Atlas-specific workflow boundaries.

## Editorial Disclosure

Submitted as an independent community agent entry by `MkDev11`. This listing is
based on Atlas official documentation and repository metadata, with no paid
placement, referral link, or affiliate relationship.

## Sources

- Atlas docs: https://atlasgo.io/docs
- Verifying migration safety: https://atlasgo.io/versioned/lint
- Migration analyzers: https://atlasgo.io/lint/analyzers
- Drift detection: https://atlasgo.io/versioned/drift-detection
- CI/CD setup: https://atlasgo.io/versioned/setup-cicd
- Applying schema migrations: https://atlasgo.io/versioned/apply
- Atlas repository: https://github.com/ariga/atlas
- Atlas latest release checked: https://github.com/ariga/atlas/releases/tag/v1.2.0