Operate Heroku Postgres with a safe inspection-first workflow. Use when the agent needs to provision, inspect, attach, promote, back up, restore, diagnose, or reason about credentials and data movement for Heroku Postgres.
Manage Heroku Postgres by separating inspection from destructive database changes.
Resolve this installed skill's directory first. Do not assume the current workspace contains the skill source repository.
Run the bundled helper from this skill's scripts/ directory:
python3 /path/to/heroku-postgres/scripts/postgres_snapshot.py --app <app>
If no app is known yet, run it without --app to inspect CLI and auth readiness only.
Begin with:
heroku pg:info -a <app>heroku pg:backups -a <app>heroku pg:credentials -a <app>heroku pg:psql -a <app> only when the user explicitly wants direct SQL inspectionheroku pg:diagnose -a <app> when available and appropriateUse the inspection results to identify the attached database, the current role of each attachment, and the backup posture before proposing a change.
Ask for confirmation before:
pg:push or pg:resetWhen moving data, explain source, destination, downtime risk, and rollback posture first.
references/postgres-ops.md for command catalogs, safety gates, and source links.