Schema Evolve
- 1 installs
- Updated July 5, 2026
- ai-digital-architect/ccode-customize
schema-evolve is a Claude Code skill that evolves a database schema through a gated pipeline of diff, migration generation, compatibility check, and rollout plan.
About
schema-evolve is a Claude Code skill that runs a database schema change through a gated pipeline. It diffs the current schema against the requested change, generates up/down migration scripts, checks backward compatibility and reversibility, then produces a rollout plan. A developer uses it for any schema change that needs a safe, reviewable migration path, and the skill halts if the migration cannot be reversed.
- Gated 4-stage schema-change pipeline: diff, generate migration, compatibility check, rollout plan
- Stops and reports if a migration is not reversible
- Ends by presenting the full plan for human review
Schema Evolve by the numbers
- 1 all-time installs (skills.sh)
- Ranked #765 of 911 Databases skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
schema-evolve capabilities & compatibility
- Capabilities
- schema migration · migration generation · compatibility check
- Use cases
- database · devops
- Pricing
- Free
What schema-evolve says it does
Evolves database schema through a gated pipeline: diff → generate migration → check compatibility → produce rollout plan.
If the migration is NOT reversible, STOP and report the issue.
Present the complete plan for human review.
npx skills add https://github.com/ai-digital-architect/ccode-customize --skill schema-evolveAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | July 5, 2026 |
| Repository | ai-digital-architect/ccode-customize ↗ |
What it does
Turn a database schema change into a diff, reversible migration, compatibility check, and rollout plan.
Who is it for?
Making a database schema change with a safe, reviewable migration and rollout plan.
Skip if: Non-database changes or migrations that do not need compatibility gating.
When should I use this skill?
A developer needs to alter a database schema and wants a gated, reversible migration path.
What you get
A diff, up/down migration, compatibility report, and rollout plan presented for human review.
- diff.json
- up/down SQL migration
- compat-report.json
By the numbers
- 4-stage gated pipeline (diff, migration, compatibility, rollout)
Files
Evolve database schema: $ARGUMENTS
Stage 1: Schema Diff
Invoke schema-differ to compare current schema against the requested change. Output: .claude/schema/diff.json
Stage 2: Generate Migration
Invoke migration-generator to produce up/down migration scripts. Output: migrations/<timestamp>_<name>.sql
Stage 3: Compatibility Check
Invoke compat-checker to verify backward compatibility and reversibility. Output: .claude/schema/compat-report.json If the migration is NOT reversible, STOP and report the issue.
Stage 4: Rollout Plan
Invoke rollout-planner (or produce inline) to create a deployment plan. Output: .claude/schema/rollout-plan.md
Present the complete plan for human review.
Related skills
Lark BaseLet their coding agents read from, write to, and query structured data stored in Lark Base (Feishu) spreadsheets and databases.493k
Azure KustoRun fast KQL queries against Azure Data Explorer for log analytics, telemetry, and time-series data.484k1.3k
Lark SheetsCreate, read, update, and export spreadsheets inside Lark (Feishu) directly from their AI coding agent.389k15.9k
Supabase Postgres Best PracticesAutomatically apply Supabase Postgres performance rules during query writing, schema design, and database optimization.313k2.4k
Firebase Data ConnectGenerate complete, production-ready Firebase Data Connect GraphQL schemas and queries for complex relational data models.112k392Firebase FirestoreAdd Cloud Firestore read/write capabilities to an Android Kotlin app using the official Firebase SDK.77k392FAQ
What are the pipeline stages?
Schema diff, generate migration, compatibility check, and rollout plan, each validating before the next proceeds.
What happens if a migration is not reversible?
The compatibility stage stops and reports the issue instead of proceeding.