postgres

Postgres

Use <skill-root>/scripts/postgres for application databases configured by .skills/postgres/config.toml (legacy: .skills/postgres/postgres.toml). Resolve the project and profile before connecting; verify database identity before consequential queries and whenever the target changes. Ask for a target only when configuration and the conversation leave it ambiguous.

Default remote access to read-only. Applying writes or DDL requires authorization for that operation and database; an explicit request can supply it. Preparing requested SQL and relevant verification does not require another approval. Before an unauthorized application, present the SQL and verification so the user can approve a concrete change. Local profile access guards do not replace server roles, grants, or RLS.

SQL-file layout, changelog format, migration-runner selection, and release ordering are project- or team-level decisions. Follow the consuming repository's instructions; do not infer a prerelease/changelog convention from this skill.

Routes

• Commands, connection setup, JSON: runtime usage.
• Config choices: options and config schema.
• Environment variables: environment.
• Inspection queries and database identity: common workflows.
• Schema changes: schema-change guardrails.
• Local connection recovery: recovery.
• Schema, query, security, concurrency, or diagnostics design: design map.
• Version-sensitive syntax: SQL version router.
• Foreign tables: FDW versions.
• Extensions: read the matching guide for PostGIS, pgvector, pg_cron, pgmq, or pg_durable.

Choose syntax supported by the oldest deployed major. If unknown, use portable SQL or state the minimum version and fallback. Load full version catalogs only for an upgrade comparison or a feature missing from the router; verify current release status before relying on PostgreSQL 19.

Ordinary commands normalize config in memory; persist changes only through an intended config-write command or documented opt-in. Use --json doctor for runtime diagnosis. Dump, restore, export, and schema diff are outside this launcher's coverage. Raw psql remains available for those operator workflows, repo-documented container/smoke checks, an explicit user choice, or launcher recovery; do not silently bypass the configured application profile.