메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 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 | infra-logs |
| description | 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. |
| argument-hint | [service-name] [environment] |
| allowed-tools | Bash, AskUserQuestion |
| model | sonnet |
Search and analyze logs from pods in the cluster. Supports filtering by time, error patterns, and entities.
Read namespace from the project's CLAUDE.md (## Infrastructure section).
# Find pods for a service
kubectl --context=<env> get pods -n <namespace> | grep <service>
kubectl --context=<env> logs <pod> -n <namespace> --since=<duration> 2>&1 \
| grep -i "error\|exception\|fail" | tail -50
Duration examples: 5m, 30m, 1h, 3h, 24h
kubectl --context=<env> logs <pod> -n <namespace> --since=<duration> 2>&1 \
| grep -i "<entity>\|<operation>" | grep -i "error" | tail -30
kubectl --context=<env> logs <pod> -n <namespace> --since=<duration> 2>&1 \
| grep -B5 -A5 -i "error\|exception" | tail -80
kubectl --context=<env> logs -f <pod> -n <namespace> | grep -i "<pattern>"
kubectl --context=<env> logs -l app=<service> -n <namespace> --since=<duration> 2>&1 \
| grep -i "error" | tail -50
kubectl --context=<env> logs <pod> -n <namespace> --previous | tail -100
Summarize findings:
If no errors found, say so explicitly — don't assume the absence of evidence is evidence of absence. Suggest checking a wider time range or different pod.