postgresql-db

Validates PostgreSQL schema naming for snake_case, prefixes, and reserved keywords.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/namnh240795/automation-with-claude-cli --skill postgresql-db
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgresql-db
Source: https://github.com/namnh240795/automation-with-claude-cli/tree/main/skills/postgresql-db
Command: npx skills add https://github.com/namnh240795/automation-with-claude-cli --skill postgresql-db

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps teams design PostgreSQL schemas with strict, consistent naming conventions, ensuring snake_case for all tables and columns, a project-specific prefix, avoidance of reserved keywords, and adherence to PostgreSQL best practices. It also includes a schema validator that can auto-correct names.

Core Features & Use Cases

  • Snake_case for all tables and columns
  • Project prefix enforcement for all tables
  • Reserved keyword avoidance and name validation
  • Schema validation and automatic name correction
  • Useful for designing robust, maintainable databases across services

Quick Start

Run the PostgreSQL naming validator on a JSON schema by executing: python3 scripts/schema_validator.py '<json_schema>' [project_prefix]

Frequently Asked Questions about postgresql-db

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

FAQPage Schema
How do I enforce snake_case naming conventions in a PostgreSQL schema?

To enforce snake_case naming in a PostgreSQL schema, you can run a Python-based validator that checks table and column names against strict formatting rules, returning structured errors and suggested corrections.

How do I validate table prefixes and reserved keywords in SQL scripts?

Validating table prefixes and reserved keywords in SQL scripts involves applying a schema validator that checks for project-specific prefixes and flags restricted names, returning structured errors for quick correction.

Can I automatically correct PostgreSQL column names that violate database design rules?

Yes, you can correct PostgreSQL column names that violate database design rules by running a schema validator that identifies invalid names and provides suggested corrections for your migration workflow.

What is the best way to check foreign key references in a JSON schema representation?

Checking foreign key references in a JSON schema representation requires a validation script that parses the schema structure, verifies naming consistency like snake_case, and validates foreign key references.

Does the PostgreSQL naming validator support migration workflows?

Yes, the PostgreSQL naming validator supports migration workflows by validating table and column names across schemas, JSON representations, and SQL scripts to ensure strict database design consistency.