القائمة
Analyzes crashing, restarting, or OOMKilled Docker/Kubernetes containers. Fixes crash causes. Do NOT use for deployment failures, app bugs, or infrastructure.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | container-crash-analysis |
| description | Analyzes crashing, restarting, or OOMKilled Docker/Kubernetes containers. Fixes crash causes. Do NOT use for deployment failures, app bugs, or infrastructure. |
| version | 1.1.0 |
| time_saved | Manual: 1-3h | With skill: 15-30m |
| license | Proprietary — Personal Use Only |
| category | debugging |
| complexity | Advanced |
| tokens | ~5000 |
| tags | ["container","docker","kubernetes","pod","oomkilled","crash","debugging"] |
| author | vheins |
Analyze container/pod failures to identify root causes (OOM, probes, config) and provide targeted fixes.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | e.g., "Docker + Kubernetes" |
container_logs | string | Yes | Logs, symptoms, or exit codes |
pod_description | string | No | kubectl describe pod output |
context | string | Yes | Limits, changes, crash frequency |
top pod or VPA.| Case | Strategy |
|---|---|
| Intermittent | Recommend persistent monitoring for leaks; check graceful shutdown. |
| Init Containers | Use kubectl logs -c for init; diagnose as a separate block. |
| High Load OOM | Recommend Vertical Pod Autoscaler (VPA) or horizontal scaling. |
flowchart TD
A([Start: Container Crash Analysis]) --> B[Parse inputs]
B --> C{Logs available?}
C -- No --> D[Provide retrieval commands]
D --> E[Describe crash types]
C -- Yes --> F[Identify Crash Type]
F --> G{Type?}
G -- OOMKilled 137 --> H[Identify memory-consuming process]
G -- App crash 1 --> I[Find exception/panic + stack trace]
G -- Startup failure --> J[Check config/port/dependency]
G -- Liveness failure --> K[Check endpoint/port/startup]
G -- CrashLoopBackOff --> L[Identify repeating crash]
G -- Segfault 139 --> M[Analyze core dump]
H --> N[Increase limit/fix leak]
I --> O[Fix exception/handling]
J --> P[Add config/port/init container]
K --> Q[Adjust timing/endpoint/startupProbe]
L --> R[Fix root cause]
M --> S[Check native deps]
N & O & P & Q & R & S --> T[Show corrected config]
T --> U{Resource crash?}
U -- Yes --> V[Right-size:\nkubectl top\nRequests=50-70%\nVPA]
U -- No --> W
V --> W[Setup alerts:
Restarts>3/10m
OOMKilled
CrashLoopBackOff]
W --> X([Output: 5 Sections + Config + Monitoring])
@upstash/context7-mcp: Library documentation and examples.| Version | Date | Description |
|---|---|---|
| 1.1.0 | 2026-03-20 | Restructured: moved examples, references, added compatibility/license |
| 1.0.0 | 2026-03-20 | Initial release |