When a statement fails—or worse, runs slowly —most of us fall back to the same old tools: EXPLAIN , manual logging, or copy-pasting into a GUI. But there is a newer, sleeker command-line utility that deserves a spot in your toolkit: .

Have you used stmtk in production? What’s your favorite hidden flag? Let me know in the comments. Note: This post is based on the conceptual tooling pattern of stmtk . For the actual latest commands and installation instructions, check the official repository.

It treats SQL as code , not just as a string to ship over a wire. For platform engineers, DBREs, and backend developers who hate guessing games, stmtk is a breath of fresh air.

Copy the slow query from logs -> Paste into EXPLAIN -> Stare at sequential scan -> Guess which index to add -> Deploy -> Pray.

echo "SELECT * FROM orders WHERE total > 100" | stmtk analyze --dialect generic stmtk won't replace your database monitoring stack. It won't tune your work_mem for you. But it will fill the gap between "I typed a query" and "The query ran."