// Use when needing to query a PostgreSQL database in DEV or PROD, check if records exist, count rows, inspect data, or run read-only SQL queries from within the cluster. Use when user says "consulta la BD", "query", "busca en la tabla", "check database", "db query", or "existe este registro".
Use when creating, updating, or compacting Architecture Decision Records (ADRs). Use when user says "adr", "crear ADR", "create ADR", "actualizar ADR", "update ADR", "compactar ADR", "compact ADR", "registrar decision", "record decision", "decision record".
Use when user asks to deploy to production, check what's deployed, find a docker image tag for a PR, or trigger a production deployment. Use when user mentions "deploy", "prod", "production", "release", or "ship".
Use when checking pod logs, searching for errors, viewing recent log output, or debugging runtime issues in DEV or PROD. Use when user says "logs de", "ver logs", "qué errores hay", "check logs", "show errors", or mentions log analysis of a service.
Use when user asks to run database migrations, create tables, apply schema changes, or mentions "migration" in the context of DEV or PROD environments. Use when user mentions "migrate", "migration:up", "create table", or "schema changes" for remote environments.
Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".
Use when doing comprehensive ticket analysis before implementation. Analyzes Jira ticket, Figma designs, Confluence/Notion docs, and codebase to produce a data map where every field is questioned and scope is explicitly defined. Use when user says "analiza ticket", "ticket analysis", "prepara ticket", "revisar ticket completo", or "qué falta en este ticket".
| name | db-query |
| description | Use when needing to query a PostgreSQL database in DEV or PROD, check if records exist, count rows, inspect data, or run read-only SQL queries from within the cluster. Use when user says "consulta la BD", "query", "busca en la tabla", "check database", "db query", or "existe este registro". |
| argument-hint | [query description] [environment] |
| allowed-tools | Bash, Read, AskUserQuestion |
| model | sonnet |
Execute read-only SQL queries against PostgreSQL databases via PgBouncer from within application pods. No psql available — use the pg module via node -e.
Read project-specific values from the project's CLAUDE.md (## Infrastructure section):
require('/app/node_modules/pg') — module is not in the global node path.development.config.js for DEV, production.config.js for PROD (both files exist in every pod).kubectl --context=<ctx> get pods -n <namespace> | grep <app-label>node -eSee scripts/query.js for the reusable helper (copy to pod with kubectl cp).
See references/query-examples.md for command templates.
| Mistake | Prevention |
|---|---|
| Not reading CLAUDE.md | Namespace, context, DB name vary per project. |
Parameterized queries ($1::uuid[]) | PgBouncer rejects them. Use inline SQL. |
require('pg') fails | Use require('/app/node_modules/pg'). |
| Wrong config file | production.config.js in a DEV pod points to PROD db. Use development.config.js for DEV. |
| Write queries without confirmation | Always ask before INSERT/UPDATE/DELETE. |