ci-debug-workflow

Debug CI failures and reproduce bugs locally across Linux and containerized environments.

35|2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/spences10/claude-code-toolkit --skill ci-debug-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-debug-workflow
Source: https://github.com/spences10/claude-code-toolkit/tree/main/plugins/devops-skills/skills/ci-debug-workflow
Command: npx skills add https://github.com/spences10/claude-code-toolkit --skill ci-debug-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debugging CI pipelines typically is slow and error-prone; this Skill helps you quickly identify failing steps, reproduce issues locally, and accelerate fixes.

Core Features & Use Cases

  • Gather CI context and error messages from logs
  • Reproduce failures locally using the same commands and environments
  • Apply targeted fixes and verify CI green status
  • Use reference materials to diagnose common patterns (dependency mismatches, missing env vars, platform differences)

Quick Start

Describe a failing CI scenario and let the workflow guide you through debugging steps.

Frequently Asked Questions about ci-debug-workflow

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

FAQPage Schema
How do I reproduce a CI pipeline failure locally?

To reproduce CI failures locally, describe the failing scenario to get structured guidance with deterministic commands and troubleshooting patterns that mirror your containerized Linux environment for accurate local reproduction.

Why does my container fail to start in CI but works locally?

Container startup failures often stem from platform differences, missing environment variables, or dependency mismatches. Use reference materials to diagnose common patterns and apply structured troubleshooting to resolve the discrepancies.

What is the best way to debug failing CI pipelines across different environments?

Debugging failing CI pipelines involves gathering error logs, reproducing issues locally with matching commands, and applying targeted fixes. This structured workflow accelerates identification of dependency mismatches and platform-specific differences.

Can I use this workflow for Linux and containerized environments?

Yes, this workflow applies to reproducible bug scenarios across Linux and containerized environments, helping you diagnose failing pipelines and containers that won't start using deterministic commands and log references.

How do I diagnose missing environment variables in CI pipelines?

Diagnose missing environment variables in CI pipelines by gathering CI context from logs and using reference materials to identify common patterns, then reproduce the failure locally to verify the fix.