القائمة
Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | error-reading |
| description | Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis |
This skill works entirely from pasted content. No local files needed.
Classify what you're looking at:
Never stop at the first error line. Scan for:
State clearly:
Error reading identifies the problem. Systematic debugging finds the root cause and fixes it. After reading the error, invoke systematic-debugging if a fix is needed.
| Error | Meaning |
|---|---|
CrashLoopBackOff | Container keeps crashing on start — check kubectl logs --previous |
OOMKilled | Container exceeded memory limit |
ImagePullBackOff | Can't pull the image — wrong name, tag, or registry auth |
Pending | No node has enough resources or matching node selector |
CreateContainerConfigError | Bad env var, missing secret or configmap |
| Error | Meaning |
|---|---|
no space left on device | Disk full — run docker system prune |
port is already allocated | Port conflict — find and stop the other process |
exec format error | Wrong architecture (e.g., ARM image on AMD64) |
| Error | Meaning |
|---|---|
502 Bad Gateway | Upstream is down or not responding |
503 Service Unavailable | No healthy upstream servers |
504 Gateway Timeout | Upstream took too long — check proxy_read_timeout |
upstream connect error | Wrong upstream address, port, or firewall blocking |
| Error | Meaning |
|---|---|
Error acquiring the state lock | Another process holds the lock — check for stuck runs |
ResourceAlreadyExists | Resource exists outside Terraform state — import it |
UnauthorizedOperation | IAM permissions missing |
InvalidInstanceType | Instance type not available in that region |
| Error | Meaning |
|---|---|
AccessDenied | IAM policy missing required action |
ThrottlingException | API rate limit — add retry logic with backoff |
InvalidClientTokenId | Wrong AWS credentials or region |
| Error | Meaning |
|---|---|
Process completed with exit code 1 | A step failed — read that step's logs |
Context access might be invalid | Wrong secret name or env var reference |
Resource not accessible by integration | Missing permissions in workflow YAML |
Use before any DevOps build, change, or new feature — refine requirements through dialogue before touching infrastructure or code
Use when working with Docker — building images, writing Dockerfiles, debugging container issues
Use to execute a written implementation plan via subagents with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when working with Kubernetes or Helm — authoring, reviewing, hardening, or debugging manifests, Deployments, Services, Ingress, RBAC, NetworkPolicy, or cluster operations
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
