ci-pipeline-debug

Locates failing CI job definitions and reproduces errors locally.

1|Updated Jun 11, 2026
One-click install
npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill ci-pipeline-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-pipeline-debug
Source: https://github.com/sergeyitaly/claude-skill-deployer/tree/main/skills_library/ci-pipeline-debug
Command: npx skills add https://github.com/sergeyitaly/claude-skill-deployer --skill ci-pipeline-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time wasted guessing at CI pipeline failure causes by providing a systematic workflow to locate the exact failing job definition, reproduce the error locally, and map it to a clear root cause category.

Core Features & Use Cases

  • Job Definition Location: Automatically finds the exact CI job definition across multi-file pipeline configurations, even when the root config only lists stages and includes.
  • Local Reproduction Guidance: Walks you through running the exact failing job commands locally with the correct working directory and environment variables to replicate the CI error.
  • Root Cause Categorization: Maps common CI failures (lint errors, test regressions, Terraform permission gaps, RBAC issues, stale artifacts) to their root cause and flags known external blockers before proposing fixes.
  • Use Case: For example, if your Terraform plan stage fails in CI with an authorization error, this skill helps you reproduce the plan command locally, identify if the issue is a missing permission, code error, or drift, and tell you exactly what action to take.

Quick Start

Use the ci-pipeline-debug skill to diagnose why the failing 'terraform-plan' job in your GitLab CI pipeline is throwing an authorization error and tell me exactly what fix is needed.

Frequently Asked Questions about ci-pipeline-debug

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

FAQPage Schema
How do I debug a failing CI pipeline job without guessing at log errors?

To debug a failing CI pipeline job, locate the exact job definition in your multi-file configuration, reproduce the commands locally with the correct environment, and categorize the root cause to determine if it requires a code fix or external permission changes.

Why does my Terraform plan stage fail in GitLab CI with an authorization error?

A Terraform plan stage in GitLab CI may fail with an authorization error due to missing RBAC permissions, code drift, or upstream stale artifacts. Reproduce the plan command locally to distinguish between a code-fixable issue and an external permission blocker.

How do I find the exact job definition in a multi-file GitLab CI configuration?

Finding the exact job definition in a multi-file GitLab CI configuration requires tracing included files from the root configuration. This systematic location process identifies where the failing stage is defined before you attempt local reproduction.

Can I reproduce a failing CI pipeline command locally to test fixes before pushing?

You can reproduce a failing CI pipeline command locally by running the exact job commands with the correct working directory and environment variables. This local reproduction isolates the error and confirms whether a code change or a permission adjustment is needed.

What is the best way to categorize root causes for CI pipeline failures?

The best way to categorize root causes for CI pipeline failures is to map common errors like lint failures, test regressions, and Terraform permission gaps to distinct categories, distinguishing between code-fixable issues, external blockers, and stale artifacts.

Does CI pipeline debugging work for all types of pipeline stages?

CI pipeline debugging works for lint, test, validate, build, plan, apply, and verify job types. It categorizes failures specific to these stages, helping you identify whether a deployment is blocked by code errors or external infrastructure permissions.