ci-doctor

Diagnose and resolve CI/CD pipeline and GitHub Actions failures.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/Spectaculous-Code/raamattu-nyt --skill ci-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-doctor
Source: https://github.com/Spectaculous-Code/raamattu-nyt/tree/main/.claude/skills/ci-doctor
Command: npx skills add https://github.com/Spectaculous-Code/raamattu-nyt --skill ci-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill diagnoses and resolves issues within CI/CD pipelines, GitHub Actions, test failures, and code scanning alerts, ensuring smooth and continuous integration.

Core Features & Use Cases

  • CI/CD Failure Diagnosis: Identifies root causes of broken builds and pipeline errors.
  • Test Failure Resolution: Addresses Vitest and Playwright test failures occurring in CI.
  • Code Scanning Alert Management: Triages and fixes GitHub Code Scanning (CodeQL) alerts and security vulnerabilities.
  • Use Case: When your GitHub Actions pipeline turns red due to a TypeScript error or a failing test, this Skill can pinpoint the exact issue, suggest a fix, and even apply it.

Quick Start

Use the ci-doctor skill to fix the broken CI build by analyzing the latest workflow logs.

Frequently Asked Questions about ci-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix failing GitHub Actions workflows caused by TypeScript errors?

To fix failing GitHub Actions workflows caused by TypeScript errors, diagnose the pipeline failures by analyzing workflow logs, applying targeted code corrections, and verifying changes locally before pushing.

How do I resolve Vitest and Playwright test failures occurring in CI?

To resolve Vitest and Playwright test failures in CI, diagnose the failing test execution logs to pinpoint the exact issue, apply the necessary fixes to the test or code, and verify locally before pushing.

How do I triage and fix GitHub CodeQL security vulnerabilities and code scanning alerts?

To triage and fix GitHub CodeQL security vulnerabilities and code scanning alerts, analyze the security alerts, apply the required code resolutions to address the vulnerabilities, and verify the changes locally.

Can I use this approach to fix broken CI/CD pipelines with dependency problems?

Yes, you can fix broken CI/CD pipelines with dependency problems by diagnosing the root causes of the pipeline errors, applying fixes to resolve the dependency issues, and verifying locally before pushing changes.

Why does my CI/CD pipeline turn red due to linting issues and how do I resolve them?

Your CI/CD pipeline turns red due to linting issues when code formatting or style checks fail, which you can resolve by diagnosing the linting errors, applying fixes, and verifying locally before pushing changes.