More screenshots

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    Pipeline Failure RCA

    1

    Turn messy CI/CD, Docker, and Kubernetes failure logs into an evidence-backed Root Cause Analysis and a safe, human-run recovery plan.

    $15

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Pipeline Failure RCA

    Pipeline Failure RCA

    Example session with this skill installed

    Context: GitLab CI → deploy payments-api to staging Kubernetes (EKS).
    Symptom: deploy:staging job fails; pods never Ready. Production not involved.

    kubectl get pods -n payments-staging:
    payments-api-7f8c9d4b6-xk2m1 0/1 CrashLoopBackOff 6 11m
    payments-api-5a1b2c3d4-m8n7w 1/1 Running 0 2d

    kubectl describe (excerpt):
    Readiness probe failed: HTTP probe failed with statuscode: 500
    Back-off restarting failed container payments-api

    kubectl logs --previous (excerpt):
    ERROR config validation failed: missing required env STRIPE_WEBHOOK_SECRET
    FATAL refusing to start with invalid config
    process exit code=1

    GitLab CI / Helm (tail):
    helm upgrade --install payments-api ... --set image.tag=2.14.0 --wait --timeout 5m
    Error: UPGRADE FAILED: context deadline exceeded
    ERROR: Job failed: exit code 1

    • Read your context and instructions
    • Compiled the pipeline failure rca
    • Generated the document

    Pipeline Failure RCA Report

    1. Executive Summary

    The staging Helm rollout for payments-api:2.14.0 failed because new pods enter
    CrashLoopBackOff: process exits with code 1 after config validation fails on
    missing STRIPE_WEBHOOK_SECRET, readiness probes return HTTP 500, and
    helm upgrade --wait times out. Old pods remain healthy; production was not touched.

    2. Root Cause Analysis (Evidence-Backed)

    | Failure Domain | Specific Error | Log Evidence |
    | Infrastructure / Config | Missing required env | missing required env STRIPE_WEBHOOK_SECRET |
    | Runtime | Exit code 1 | refusing to start with invalid config |
    | Kubernetes Health | Readiness 500 | HTTP probe failed with statuscode: 500 |
    | CI/CD Deploy | Helm wait timeout | UPGRADE FAILED: context deadline exceeded |

    3. Immediate Recovery Plan (human-run only)

    1. Inspect Secret + Deployment env refs in payments-staging
    2. Apply STRIPE_WEBHOOK_SECRET from vault (never commit secrets)
    3. helm upgrade … --wait; verify READY 1/1 and /health 200
    4. If blocked: helm rollback payments-api -n payments-staging

    4. Long-Term Prevention

    • CI pre-check for required secrets in target namespace
    • Helm lint fails when secretKeyRefs unset
    • Boot integration test with minimal env fixture

    5. Blast Radius & Rollback

    • Data impact: None (config at startup)
    • Downtime risk: Staging rollout stuck; old pod still Running
    • Rollback: helm rollback (staging only) — no namespace delete

    Incident Management JSON

    {
      "incident_type": "Kubernetes Rollout Failure",
      "severity": "Medium (Staging)",
      "failure_domain": "Infrastructure/Config",
      "root_cause_summary": "payments-api:2.14.0 CrashLoopBackOff because STRIPE_WEBHOOK_SECRET is missing; readiness 500 and helm --wait timeout.",
    

    "immediate_fix_commands": ["kubectl get secret -n payments-staging", "helm rollback payments-api -n payments-staging", "..."],
    "prevention_tags": ["kubernetes", "helm", "secrets", "crashloopbackoff", "gitlab-ci"]
    }

    pipeline-failure-rca.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    GitHub Actions / GitLab CI / Jenkins job failed — need root cause fastDocker build or container exit 137 / 143 / 1Kubernetes CrashLoopBackOff, ImagePullBackOff, probe failuresHelm / cloud deploy timeout or rollbackStaging rollout stuck while old pods still runStakeholder-ready incident summary + prevention list

    About this skill

    The problem

    Failed deploys dump hundreds of lines of CI, Docker, and Kubernetes noise. Teams lose time scrolling for the real error code, guess the root cause, and sometimes apply unsafe “fixes” under pressure.

    What it does

    Pipeline Failure RCA turns raw failure evidence into a structured report:

    • Executive summary of what failed and where
    • Evidence-backed RCA with log quotes and failure domain
    • Immediate recovery plan (unblock) + verification steps
    • Long-term prevention recommendations
    • Blast radius and rollback assessment
    • Incident Management JSON for tickets / status pages

    Frameworks & tools

    • GitHub Actions, GitLab CI, Jenkins, CircleCI log triage
    • Docker exit codes (e.g. 137 OOM, 143 SIGTERM, 1)
    • Kubernetes CrashLoopBackOff, ImagePullBackOff, probe failures
    • Common patterns: OOM, peer deps, IAM 403, missing config/secrets
    • Production safety rules: fix-forward vs rollback, no destructive recovery

    Why this beats prompting it yourself

    • Every RCA claim must cite log evidence — less hand-waving
    • Pattern library for frequent DevOps failure modes
    • Safety gate rewrites unsafe recovery suggestions
    • Blast radius + rollback decision matrix built in
    • JSON artifact for incident tooling — not only a chat essay
    • Strict read-only: analysis only, human executes

    Use cases

    • Broken CI build or deploy stage
    • Container OOM or crash on start
    • K8s rollout stuck / CrashLoopBackOff
    • Cloud/IAM deploy permission errors
    • Fast RCA for engineering managers and on-call

    Known limitations

    • Quality depends on the logs you provide (truncated logs lower confidence)
    • Does not connect to clusters or CI systems by itself
    • Does not execute remediation commands
    • Not a substitute for on-call judgment on production data-path incidents

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Needs access to

    Api

    Listed1 month ago

    What's inside

    Frequently Asked Questions