schema-audit-agent

Audits database schema and migrations for drift against project conventions.

Updated Jun 17, 2026

Search Tags:#database migration #drift detection #ddev #read-only #model checker #schema audit

Ready to run

npx skills add https://github.com/ndestates/ndestates-website --skill schema-audit-agent-ndestates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: schema-audit-agent
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/schema-audit-agent
Command: npx skills add https://github.com/ndestates/ndestates-website --skill schema-audit-agent-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Detecting drift between database schemas, migrations, and model definitions is tedious and error-prone when done manually. This Skill performs read-only schema and migration audits for the ndestates-io project, surfacing mismatches before they cause production issues. ## Core Features & Use Cases - Schema Drift Detection: Compares live database schema against model definitions and migration history to find mismatches. - Read-Only Safety: Runs only safe DDEV inspection commands against a test database, never executing changes. - Structured Reporting: Produces structured output listing mismatches, migration references, and associated risks. - Use Case: Before deploying a new feature touching the Property models, invoke the audit to verify recent migrations align with model definitions and identify any risky drift. ## Quick Start Invoke the schema audit agent with a scope such as "valuations" or "recent migrations" to receive a structured drift report.

Frequently Asked Questions about schema-audit-agent

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

FAQPage Schema

How do I audit database schema drift in my project?▼

Invoke the schema-audit-agent with a scope such as a table name, model pattern, or "recent migrations". It loads project conventions, inspects the test database read-only via DDEV, and returns a structured report of mismatches and risks.

How to check migrations against model definitions?▼

Provide a scope like "Property* models" when invoking the audit. The agent compares migration history against model definitions using the project's model checker configuration and reports any drift with migration references.

Does the schema audit modify the database?▼

No, the audit is strictly read-only. It runs safe DDEV inspection commands against a test database and never executes schema changes, following the project's data safety rules.

What scopes can I pass to the schema audit?▼

You can pass table names like "valuations", model patterns like "Property* models", or "recent migrations". The argument-hint field documents these accepted scope formats.

When should I not use a read-only schema audit?▼

Do not use it when you need to apply or generate migrations, since it never executes changes. It is designed for drift analysis and risk reporting, not for schema modification or data repair.