Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    CI/CD Pipeline Failure Fixer

    1

    Diagnose CI/CD failures, analyze build logs, and generate corrected pipeline configurations across all major platforms.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    CI/CD Pipeline Failure Fixer

    CI/CD Pipeline Failure Fixer

    Example session with this skill installed

    My GitHub Action just failed on the 'test' job. Here is my action.yml and the log output showing an exit code 127 after the 'npm install' step. Can you find the root cause and fix it?

    • Read your context and instructions
    • Compiled the ci cd pipeline

    The pipeline failed during the test stage because the npm command was not found in the runner environment. While npm install succeeded in the previous setup step, the test job was missing the necessary actions/setup-node configuration to persist the environment or was running on a different container without Node.js installed.

    Pipeline Failure Summary

    • Platform: GitHub Actions
    • Failed pipeline: CI Workflow
    • Failed stage: test
    • Failure type: Environment/Runtime
    • Root-cause confidence: High
    • Primary evidence: exit code 127 (Command not found) for npm in the test job log.

    Stage Map

    StageStatusDependencyKey Observation
    checkoutSuccessNoneRepository cloned successfully.
    buildSuccesscheckoutnpm install completed on a hosted runner.
    testFailedbuildnpm command not recognized.

    Root-Cause Analysis

    Issue — Missing Node Runtime in Test Job

    • Status: Confirmed
    • Evidence: Log shows sh: npm: command not found.
    • Root Cause: The test job is defined as a separate job from build but does not include the actions/setup-node step or a container image containing Node.js.
    • Why It Happens: GitHub Action jobs run on fresh runners unless explicitly configured otherwise.
    • Affected Stage: test

    Corrected Configuration

    jobs:
  test:
    runs-on: ubuntu-latest
    needs: build
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test

    Required Environment Variables & Secrets

    NameTypeRequired?ScopePurposeAction
    NODE_AUTH_TOKENSecretOptionalnpm-registryFor private packagesCheck Repo Secrets

    Next steps

    1. Add the setup-node step to the test job in your action.yml.
    2. Ensure npm ci is used for consistent dependency installation in CI.
    3. Rerun the failed job to verify the npm command is available.

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

    What you get

    Diagnose exit code errors and stack traces in build logs.Fix YAML syntax and logic errors in GitHub Actions or GitLab CI.Identify missing environment variables and required secrets.Resolve dependency and caching issues that break builds.

    About this skill

    The problem

    CI/CD failures often produce opaque logs that lead to hours of trial-and-error debugging. Developers struggle to distinguish between intermittent environment flakes, missing secrets, and actual configuration syntax errors.

    What it does

    • Analyzes pipeline YAML and build logs to pinpoint the first meaningful failure point.
    • Traces stack traces and exit codes to separate root causes from downstream cascade errors.
    • Identifies missing or misconfigured environment variables and secrets without exposing sensitive values.
    • Generates minimal, corrected configuration snippets for GitHub Actions, GitLab CI, Jenkins, and more.
    • Provides actionable verification steps to reproduce and fix the failure locally or in-pipe.

    Frameworks & tools

    GitHub Actions, GitLab CI/CD, Jenkins, CircleCI, Bitbucket Pipelines, and Azure Pipelines. Supports Dockerfiles, dependency files (npm, pip, maven), and shell scripts.

    Why this beats prompting it yourself

    Generic LLMs often hallucinate fixes or suggest unrelated refactors. This skill follows a strict forensic workflow that prioritizes evidence from logs over guesswork, ensuring you get the smallest safe change required to green the build.

    Use cases

    • Debugging "Permission Denied" errors in containerized CI runners.
    • Fixing broken "needs" dependencies and artifact passing between stages.
    • Resolving version mismatches between local environments and CI agents.
    • Identifying missing repository secrets that cause silent deployment failures.

    Known limitations

    Cannot access private external logs or secret values directly. Requires manual provision of log snippets or YAML files if the agent lacks repository access.

    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 4 days ago

    • Passed all security checks, Safe to install

    Listed4 days ago

    What's inside

    Frequently Asked Questions