Database Migration Review with Claude Code: Result JSON Schema
A production playbook for database migration review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Backend teams shipping schema changes
The problem
Backend teams shipping schema changes need database migration review to run repeatedly against migration files, ORM models, production query samples, and rollback notes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the database migration review skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For database migration review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "database migration review completed",
"body": { "type": "database_migration_review", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo