moai-lang-sql

SQL best practices are enforced using sqlfluff 3.2 for linting and style checks, pgTAP for test coverage, and migration-management workflows. This Skill integrates these tools to catch quality issues in code reviews and CI pipelines, ensuring consistent standards across PostgreSQL and MySQL projects.

Yes. pgTAP enables test-driven development for SQL by validating query logic and migration scripts. This Skill provides pgTAP patterns and guidance to build robust test coverage, ensuring migrations execute correctly and queries behave as expected before deployment.

Migration management combines version-controlled up/down scripts with automated validation. This Skill guides you through consistent migration workflows, lint checks via sqlfluff, and test coverage via pgTAP to prevent breaking changes and maintain data integrity across environments.

Yes. sqlfluff 3.2 supports both PostgreSQL and MySQL syntax. This Skill applies sqlfluff rules to enforce dialect-specific best practices, catch style violations, and suggest query optimizations in manual audits and automated CI pipelines.

Consistent migrations require standardized naming, version enforcement, and automated validation. This Skill enforces tool versions, integrates TDD workflows, and applies quality gates via moai-foundation-trust to guarantee all team migrations meet TRUST 5 compliance and robustness standards.

SQL linting focuses on style, syntax, and testability rather than runtime performance at scale. This Skill provides lint results and migration guidance but does not replace load testing or query profiling for high-volume workloads; use it alongside optimization patterns for production queries.