CI/CD Doctor — Fix or Generate GitHub Actions

    0

    Diagnose failing GitHub Actions from logs, or draft a minimal green pipeline — confirm before every workflow write.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    CI/CD Doctor — Fix or Generate GitHub Actions

    Example session with this skill installed

    CI failed on my last push. Can you check why the build job is red and fix it?

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

    I have analyzed the failing run for the main branch. It looks like a dependency mismatch in the build step.

    CI Doctor report

    Mode: fix
    Symptom: npm install failed with an engine compatibility error.
    Likely cause: Node version mismatch (90% confidence)
    Evidence: The workflow uses node-version: 20 but package.json specifies engines: { "node": ">=22" }. This caused the Setup Node.js step to pass but the Install dependencies step to exit with code 1.

    Fix / draft plan

    1. Read-only: Verify package.json engine requirements.
    2. Needs confirm: Update .github/workflows/ci.yml to use node-version: 22.

    Needs confirm: Update actions/setup-node to @v4 to ensure compatibility with newer Node versions if not already pinned.

    
    # Proposed patch for .github/workflows/ci.yml
    jobs:
      build:
        runs-on: ubuntu-latest
        steps:
          - uses: actions/checkout@v4
          - name: Use Node.js
            uses: actions/setup-node@v4
            with:
              node-version: '22'
              cache: 'npm'
          - run: npm ci
          - run: npm run build
    

    Next steps

    1. Approve the YAML update to node-version: 22.
    2. Run gh workflow run ci.yml to trigger a manual test.
    3. Monitor the progress with gh run watch.

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

    About this skill

    CI/CD Doctor turns red GitHub Actions X marks into a ranked diagnosis — or scaffolds a lean CI file.

    • Scan order: run to job to step to YAML to secrets (names only)
    • Failure matrix for lockfiles, Node versions, permissions, OIDC
    • Generate mode: minimal Node/pnpm templates, shown before write
    • Confirm before editing .github/workflows files

    You get SKILL.md plus GHA scan guide, failure matrix, workflow templates, and test prompts.

    Cannot view or set secret values. User must manually configure OIDC, self-hosted runners, and branch protections. Focuses on GitHub Actions only.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    Python

    Permissions

    Read Files
    Write Files
    Network Access
    Listed27 days ago

    What's inside

    Frequently Asked Questions

    CI CD Doctor integrates with your environment to scan existing workflow YAML files and use the GitHub CLI (`gh`) to pull real-time logs, ensuring fixes are based on your specific repo state rather than generic advice.

    The skill is designed specifically for GitHub Actions; it supports major ecosystems like Node.js and Python, including complex monorepo setups and OIDC-based deployment workflows.

    No, for security reasons, the skill cannot access or view the actual values of your secrets; it only identifies if a secret is missing or misnamed based on the workflow's requirements.

    The skill requires a standard installation on an AI agent with access to your local file system and the GitHub CLI to read logs and suggest localized YAML patches.

    While the skill provides the precise YAML patch to fix a failure, it cannot bypass repository settings like Branch Protection or manually click 'Enable' on GitHub Actions in the UI.

    New in DevOps & Cloud