governing-naming-conventions

Name: governing-naming-conventions
Availability: InStock
Author: Musher

Audit PostgreSQL database objects for naming convention violations.

Updated Mar 6, 2026

Search Tags:#database #postgresql #auditing #sql #naming conventions #schema governance

Ready to run

npx skills add https://github.com/musher-dev/bundles --skill governing-naming-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governing-naming-conventions
Source: https://github.com/musher-dev/bundles/tree/main/database-schema-governance/skills/governing-naming-conventions
Command: npx skills add https://github.com/musher-dev/bundles --skill governing-naming-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for consistent and predictable naming conventions in PostgreSQL databases, preventing ambiguity, reducing cognitive load, and enabling automated linting.

Core Features & Use Cases

Comprehensive Auditing: Enforces naming rules for tables, columns, primary keys, foreign keys, booleans, timestamps, indexes, and constraints.
Standardization: Ensures adherence to snake_case, plural table names, singular column names, and specific prefixes/suffixes for different object types.
Use Case: When reviewing a new database schema, use this Skill to automatically identify and report any naming violations, ensuring consistency before deployment.

Quick Start

Use the governing-naming-conventions skill to audit the naming conventions of the 'users' table.

Frequently Asked Questions about governing-naming-conventions

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

FAQPage Schema

How do I audit PostgreSQL naming conventions for tables and columns?▼

To audit PostgreSQL naming conventions, review database objects like tables and columns to ensure they follow snake_case, plural table names, and singular column names. This identifies naming violations and enforces schema consistency before deployment.

What are the standard PostgreSQL naming rules for constraints and indexes?▼

Standard PostgreSQL naming rules for constraints and indexes require specific prefixes and suffixes alongside snake_case formatting. Enforcing these specific naming patterns reduces ambiguity and enables automated linting across your database schema.

Does this naming convention audit cover booleans and timestamps in PostgreSQL?▼

Yes, PostgreSQL naming convention auditing covers booleans and timestamps by applying specific naming patterns to these data types. It checks that boolean columns and timestamp fields adhere to standardized naming rules for schema consistency.

Can I use this to enforce snake_case and pluralization rules in an existing PostgreSQL schema?▼

Yes, you can enforce snake_case and pluralization rules on an existing PostgreSQL schema. The auditing process reviews current database objects and reports any violations against singular column names and plural table names for consistency.

What is the best way to check a PostgreSQL schema for naming standard violations before deployment?▼

The best way to check a PostgreSQL schema for naming violations is running a comprehensive audit that scans tables, columns, primary keys, foreign keys, indexes, and constraints. This reports inconsistencies and enforces naming standards prior to release.