database-schema-validator

Validate SQL schema files for snake_case tables, id primary keys, and no DROP TABLE statements.

13|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/phenobarbital/antigravity-config --skill database-schema-validator-phenobarbital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-schema-validator
Source: https://github.com/phenobarbital/antigravity-config/tree/main/backend/.agent/skills/database-schema-validator
Command: npx skills add https://github.com/phenobarbital/antigravity-config --skill database-schema-validator-phenobarbital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates SQL schema files to ensure they comply with internal safety and naming policies, reducing risky migrations and enforceable coding standards.

Core Features & Use Cases

  • Enforces that no DROP TABLE statements are present in schemas.
  • Verifies table names use snake_case and every table includes a PRIMARY KEY column named id.
  • Suitable for CI pipelines, code reviews, and schema audits to automatically detect violations and guide fixes.

Quick Start

Run the provided Python script to validate a user-supplied SQL schema file and report any policy violations.

Frequently Asked Questions about database-schema-validator

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

FAQPage Schema
How do I validate SQL schema files to block DROP TABLE statements in CI pipelines?

You validate SQL schema files by running a script that scans for and blocks DROP TABLE statements, enforcing safety policies in CI pipelines, code reviews, and schema audits to prevent risky migrations.

How do I enforce snake_case naming conventions for SQL table names?

To enforce snake_case naming, you validate the SQL schema against internal policies that require all table names to follow the snake_case format, automatically detecting and reporting any violations during schema audits.

Can I automatically check if every SQL table has an id PRIMARY KEY?

Yes, you can automatically check SQL schemas to verify that every table includes a PRIMARY KEY column explicitly named id, ensuring database design compliance before running migrations or generating schema files.

What is the best way to detect unsafe SQL schema changes before migration?

The best way to detect unsafe SQL schema changes is to run an automated validation script that flags policy violations like DROP TABLE statements and missing id primary keys before applying database migrations.

Do I need any external dependencies to validate SQL schemas for naming and safety policies?

No, you do not need external dependencies to validate SQL schemas for naming and safety policies, as the validation is handled by a standalone Python script that requires only your SQL schema file as input.