pgcli

database
$ pipx install pgcli
Summary

Postgres shell, autocomplete, and readable results from the terminal.

  • pgcli fits data & db well, especially for postgres shell, autocomplete, and readable results from the terminal.
  • 823 homebrew installs (30d).
  • Verify with `pgcli --version` first.
  • Best treated as a human-first terminal tool.
  • Output is mostly text-first, so verify results before scripting around it.
database-pgcli-SKILL.md

Pgcli guide

Postgres shell, autocomplete, and readable results from the terminal. Built by dbcli.

Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.

When to apply

  • postgres shell, autocomplete, and readable results from the terminal.
  • You work with databases and want a fast terminal interface.
  • You need postgres shell.
  • You need autocomplete.
  • You need readable results.

Quick reference

Installpipx install pgcli
Verifypgcli --version
First real commandpgcli postgres://localhost/postgres

Open CLI × skills.sh

Open CLI integrates pgcli with the right skills.sh companions so you get the tool and the workflow together.

Database Schema Design

Recommended pairing

Open CLI recommends this skills.sh skill because it fits database workflows. Use better schema and migration decisions when a CLI touches databases.

View on skills.sh
$ npx skills add https://github.com/supercent-io/skills-template --skill database-schema-design
Starter prompt

Use pgcli together with the Database Schema Design skills.sh skill. Inspect the current schema or data first, summarize what matters, and ask before any migration or write action.

Why this tool

  • pgcli fits data & db well, especially for postgres shell, autocomplete, and readable results from the terminal.
  • 823 homebrew installs (30d).
  • Verify with `pgcli --version` first.

Watch-outs

  • Automation can be brittle.
  • Output is mostly plain text.
  • Start with read-only or dry-run commands.

Example workflow

1. pgcli postgres://localhost/postgres

Safe start

Step 1

Install pgcli.

Step 2

Run `pgcli --version` first.

Step 3

Start with `pgcli postgres://localhost/postgres`.

Step 4

Install a CLI that matches your database engine.

Alternatives worth considering