Skill Detail
Lint PostgreSQL migrations and SQL changes before irreversible schema mistakes land with Squawk
Catch locking, indexing, and schema-change hazards in PostgreSQL migration SQL before a review turns into downtime.
Code Quality & ReviewMulti-Framework
Code Quality & Review
Multi-Framework
Security Reviewed
⭐ 1.1k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill lint-postgresql-migrations-and-sql-changes-before-irreversible-schema-mistakes-land-with-squawk
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
Squawk CLI or container image, PostgreSQL migration SQL files, and optional CI or pre-commit integration.
Install & setup
Install Squawk from the upstream CLI, package, container, or release path, point it at the migration SQL files or repository, and review the reported warnings before merging or applying schema changes.
Author
sbdchd
Publisher
Individual
Last updated
Apr 17, 2026
Quick brief
Use Squawk when an agent is reviewing PostgreSQL migrations or raw SQL files and needs a migration-safety pass, not when a user just wants a normal database client or editor. The workflow is tightly bounded: lint the migration SQL, flag risky patterns like blocking index creation or bad type choices, and return actionable fixes before merge or rollout. That scope boundary, pre-merge Postgres migration linting for operational safety, keeps it distinct from a generic Postgres product card.