review-entity-store

You audit pull requests for SQL migrations and sqlc queries by analyzing PR diffs and verifying SQL migrations, sqlc queries, and sqlc.yaml configurations against predefined project standards for domains and entities.

To ensure consistency between protobuf definitions and SQL schema, cross-reference proto definitions with the database schema during code review to identify potential data model issues and alignment deviations.

Yes, you can automatically check sqlc.yaml configurations by auditing pull requests and cross-referencing the configurations against predefined project conventions for data types and entities.

The best way to review database schema changes for naming convention deviations is to automate pull request auditing, cross-referencing SQL migrations and sqlc queries against expected schema patterns before human review.

Reviewing entity store PRs requires no specific dependencies or environments as it operates by analyzing PR diffs directly, cross-referencing changes with project conventions for domains, entities, and data types.

You should not use automated data model PR review when your project lacks predefined standards for SQL migrations and sqlc configurations, as the Skill relies on cross-referencing PR diffs against established project conventions.