Postgres

Work with a PostgreSQL database from a coding agent: inspect the real schema, write and tune queries against actual plans, and review migrations for locks and data loss before they run.

Start with /postgres-query-review <query or file> to tune a query against its real plan, /postgres-migration-review <file> before applying a migration, or just ask about the schema. The supabase-postgres-best-practices skill loads whenever tables, indexes or queries are written.

Database access goes through DBHub (https://github.com/bytebase/dbhub, MIT), run locally with npx. Export DATABASE_URL (for example postgres://user:password@localhost:5432/app) before starting your agent. Use a read-only database role: the setup's rules make the agent ask before any write, but the role is the real guard. Point it at a development or staging database, not production.

Third-party skill, imported unmodified: supabase-postgres-best-practices from https://github.com/supabase/agent-skills (MIT) — written for Postgres running anywhere, not only on Supabase. The two review skills are written by Athenode. Not affiliated with Supabase or Bytebase.

Prerequisites: Node.js and a reachable Postgres database.