// 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 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 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 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 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 | infra-migrations |
| description | 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. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, AskUserQuestion |
| model | haiku |
Run MikroORM migrations on remote environments (DEV/PROD) via port-forward to PgBouncer, since @mikro-orm/migrations is a devDependency not available in production images.
Read project-specific values from the project's CLAUDE.md (## Infrastructure section):
npm run migrations:up)digraph migrate {
rankdir=TB;
node [shape=box];
fetch [label="1. Identify migrations & source PR"];
confirm [label="2. Confirm with user"];
get_password [label="3. Get DB password from pod"];
port_forward [label="4. Port-forward (local 16432/16433)"];
run_migration [label="5. Run migration:up"];
verify [label="6. Verify no pending"];
close [label="7. Close port-forward"];
next_env [label="More envs?" shape=diamond];
fetch -> confirm -> get_password -> port_forward -> run_migration -> verify -> close -> next_env;
next_env -> get_password [label="yes"];
next_env -> done [label="no"];
done [label="Done"];
}
See references/commands.md for all shell commands per step.
Always run DEV first. If DEV fails, do NOT proceed to PROD.
| Mistake | Prevention |
|---|---|
| Running migrations inside the pod | @mikro-orm/migrations is a devDependency. Run locally via port-forward. |
| Not reading CLAUDE.md first | Contexts, namespace, DB names, and scripts vary per project. |
| Port conflict between envs | Use local port 16432 for DEV, 16433 for PROD. |
| Not quoting the password | Special chars (#, ?) — always single-quote. |
| Running PROD before DEV | Always verify DEV first. |
CheckConstraintViolationException on UPDATE | DROP CONSTRAINT IF EXISTS before the UPDATE, re-add after. |
Ghost entries in mikro_orm_migrations | Consolidated/deleted migrations — harmless, MikroORM ignores them. |