model-schema-check

Review model and database schema consistency against the test database using project cache and tooling.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ndestates/ndestates-website --skill model-schema-check-ndestates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: model-schema-check
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/model-schema-check
Command: npx skills add https://github.com/ndestates/ndestates-website --skill model-schema-check-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Detecting drift between application models and the actual database schema is error-prone and risky, especially when migrations run against live data. This Skill provides a safe, cache-first workflow to verify schema consistency strictly against the test database. ## Core Features & Use Cases - Cache-First Context Loading: Reads project conventions, testing rules, and open concerns from the local documentation cache before running any checks. - Test-DB-Only Safety: Enforces non-negotiable rules so all checks run via DDEV against the test database, never the live database. - Structured Drift Reporting: Outputs models and tables checked, mismatches in columns, types, indexes, and foreign keys, mapped to specific migration files. - Use Case: After running recent migrations on a Laravel project, ask the assistant to verify the Property model matches the test database schema and receive a safe remediation report without any destructive commands. ## Quick Start Ask the assistant to run a model schema check on the Property model against the test database after the recent migrations.

Frequently Asked Questions about model-schema-check

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

FAQPage Schema
How do I check model and database schema consistency in Laravel?▼

Run a read-only schema inspection against the test database using the project's model-schema-check tooling via DDEV. The workflow compares columns, types, indexes, and foreign keys, then maps any mismatches to specific migration files.

How to verify schema drift after running migrations?▼

After migrations, run the schema check against the test database only and review the report of models and tables inspected. Any drift is listed with references to the responsible migration files and safe remediation suggestions.

Can schema checks run against the production database?▼

No, this workflow strictly targets the test database and confirms the environment before running. Destructive commands on the live database are explicitly forbidden, and only read-only inspection is performed.

Why does the schema check require loading project cache files first?▼

The cache files contain migration rules, testing conventions, and open concerns that govern how checks must run. Loading them first ensures the inspection follows project-specific safety rules and references known schema issues.

What are the limitations of automated schema consistency checks?▼

The check only reports mismatches and suggests remediations; it never auto-executes fixes. It also depends on the availability of project cache documentation and the project's own checker tooling.