schema-agent

Plan and apply database schema migrations with integrity checks.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill schema-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-agent
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/schema-agent
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill schema-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you plan and apply database schema changes safely when a roadmap task affects the data model, reducing migration mistakes and keeping the project’s schema documentation in sync.

Core Features & Use Cases

  • Migration design: Reviews fields, relations, defaults, indexes, and delete rules before writing changes.
  • Safe execution: Applies migrations with clear guardrails, including confirmation before production-destructive actions.
  • Schema hygiene: Updates the cheatsheet and keeps generated artifacts aligned after model changes.
  • Use case: Use it when adding a new business model, modifying a relation, or auditing an existing migration before release.

Quick Start

Ask the schema agent to review the active roadmap task, propose the schema diff, and apply the migration only after I confirm the changes.

Frequently Asked Questions about schema-agent

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

FAQPage Schema
How do I plan and apply database schema migrations safely?

Database schema migrations require reviewing fields, relations, defaults, and delete rules before applying changes. You can design the schema diff, run integrity checks, and sequence migrations safely with confirmation required before any destructive production changes are executed.

What is the best way to review a data model before modifying database relations?

Reviewing a data model involves auditing existing fields, indexes, and relation rules before writing changes. This ensures ORM regeneration and data-model consistency, keeping schema documentation and generated artifacts aligned after the modification is applied.

How do I keep my schema cheatsheet updated after ORM changes?

Updating a schema cheatsheet involves regenerating ORM artifacts and syncing documentation after modifying models or fields. This maintains data-model consistency and ensures the project's schema records accurately reflect the newly applied database changes.

Can I use automated migration sequencing for destructive production database changes?

Automated migration sequencing supports destructive production database changes but requires explicit confirmation before execution. Safe execution guardrails are applied to review the schema diff and perform integrity checks to prevent accidental data loss during deployment.

When do I need to regenerate the ORM after a database schema update?

You need to regenerate the ORM after a database schema update whenever roadmap tasks modify models, fields, or relations. This regeneration ensures data-model consistency and aligns generated artifacts with the newly applied schema changes.

Why does database migration require integrity checks before deployment?

Database migration requires integrity checks to validate fields, relations, defaults, and indexes before deployment. These checks prevent schema inconsistencies and ensure safe migration sequencing, reducing the risk of migration mistakes during production releases.