// 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 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 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 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-pods |
| description | 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". |
| argument-hint | [service-name] [environment] |
| allowed-tools | Bash, AskUserQuestion |
| model | haiku |
Inspect pod status, health, events, and resource usage across cluster environments.
kubectl --context=<env> get pods -n <namespace> | grep <service>
kubectl --context=<env> get pods -n <namespace> -o wide
kubectl --context=<env> get pods -n <namespace> | grep -v "Running\|Completed"
kubectl --context=<env> describe pod <pod> -n <namespace> | tail -30
Events show recent scheduling, pulling, starting, and crash info.
kubectl --context=<env> get pods -n <namespace> -o custom-columns=\
NAME:.metadata.name,STATUS:.status.phase,RESTARTS:.status.containerStatuses[0].restartCount,\
AGE:.metadata.creationTimestamp | grep <service>
kubectl --context=<env> top pods -n <namespace> | grep <service>
kubectl --context=<env> exec -n <namespace> <pod> -- env | grep -iv "pass\|secret\|token\|key" | sort
kubectl --context=<env> get pod <pod> -n <namespace> \
-o jsonpath='{.spec.containers[0].image}'
The image tag is the GitHub Actions run ID (databaseId). To find which PR/commit it corresponds to:
# Cross-reference image tag with CI runs on main
gh run list --repo <org>/<repo> --branch main --json databaseId,displayTitle,headSha \
| jq '.[] | select(.databaseId == <image-tag>)'
Read namespace names from the project's CLAUDE.md (## Infrastructure section). Typical patterns:
plataformadato)shared-infra)kubectl --context=<env> get deploy -n <namespace> | grep <service>
⚠️ ALWAYS ask for explicit confirmation before running this command, in any environment. State clearly: what deployment will restart, in which environment, and what the impact is (brief downtime during rollout). Do NOT run without the user saying "yes", "proceed", or equivalent.
kubectl --context=<env> rollout restart deployment/<deployment> -n <namespace>
kubectl --context=<env> rollout history deployment/<deployment> -n <namespace>