debug-ci

Diagnose GitHub Actions CI/CD failures and propose remediation steps and commands.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zerdos/spike-land-nextjs --skill debug-ci-zerdos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-ci
Source: https://github.com/zerdos/spike-land-nextjs/tree/main/.github/skills/debug-ci
Command: npx skills add https://github.com/zerdos/spike-land-nextjs --skill debug-ci-zerdos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify and fix CI/CD failures in GitHub Actions across a project, reducing debugging time and restoring CI health.

Core Features & Use Cases

  • CI failure diagnosis: interpret logs, identify root causes, and propose remediation steps.
  • Workflow optimization: suggest targeted fixes for lint, type checks, tests, builds, and E2E runs.
  • Use Case: when a PR check fails on a commit, surface failing steps, error messages, and suggested commands to resolve.

Quick Start

To begin debugging CI failures, run the suggested commands, inspect the GitHub Actions logs, identify the failing step, apply fixes, and re-run the workflow to verify resolution.

Frequently Asked Questions about debug-ci

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

FAQPage Schema
How do I debug failing GitHub Actions workflows in my PR?

To debug failing GitHub Actions workflows in your PR, inspect the Actions logs to identify the failing step, apply targeted fixes for linting or tests, and re-run the workflow to verify resolution.

What is the best way to diagnose CI failures for Vercel preview deployments?

The best way to diagnose CI failures for Vercel previews is to interpret the workflow logs, identify failure patterns in builds or end-to-end tests, and execute suggested remediation commands to restore pipeline health.

How do I fix failing lint or type check steps in GitHub Actions?

You fix failing lint or type check steps in GitHub Actions by reading the error messages in the logs, applying the proposed code or configuration fixes, and pushing the commit to trigger a new workflow run.

Do I need external CI tools to diagnose GitHub Actions failures?

No, you do not need external CI tools to diagnose GitHub Actions failures; this approach requires no tooling beyond standard GitHub Actions usage to surface failing steps and suggest actionable commands.

Why does my GitHub Actions build fail on pull requests but not locally?

GitHub Actions build failures on PRs often stem from environment differences or E2E test configurations; analyze the specific CI logs to isolate the failing step and apply the recommended remediation steps.