debug-ci

Containerize CI environments to reproduce and debug local failures.

433|25|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/web-infra-dev/rslint --skill debug-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-ci
Source: https://github.com/web-infra-dev/rslint/tree/main/agents/debug-ci
Command: npx skills add https://github.com/web-infra-dev/rslint --skill debug-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce and debug CI failures locally by containerizing the CI environment, enabling reliable investigation of flaky or platform-specific issues.

Core Features & Use Cases

  • Docker-based reproducibility: Build a container that mirrors the CI environment to reproduce failures on local machines.
  • Linux-specific debugging: Address Linux-only issues (xvfb, GUI tests) and Go test failures with a predictable toolchain.
  • Use Case: When a PR fails in CI but passes locally, run this Skill to reproduce the CI steps inside a Docker container and isolate the failure.

Quick Start

Start by building the reproduction container using the Dockerfile from the project’s CI guide and run tests inside it to match the CI workflow.

Frequently Asked Questions about debug-ci

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

FAQPage Schema
How do I reproduce CI failures locally when my PR passes locally but fails in CI?

To reproduce CI failures locally, containerize the CI environment using Docker to build and run the same environment as CI. This approach mirrors the CI environment to reliably investigate flaky or platform-specific test failures on your local machine.

How do I debug Linux-specific CI failures like xvfb or GUI tests on a non-Linux machine?

To debug Linux-specific CI failures like xvfb or GUI tests on a non-Linux machine, build a Docker container that mirrors the CI environment. This provides a predictable Linux toolchain to reproduce and isolate platform-specific issues locally.

Do I need Docker to reproduce Go test failures from my CI workflow?

Yes, Docker is required to reproduce Go test failures from your CI workflow. The solution requires Docker and a reproducible CI workflow to build and run the same environment as CI, ensuring reliable investigation of divergent test results.

What's the best way to isolate flaky CI test failures that only happen on Linux?

The best way to isolate flaky CI test failures that only happen on Linux is to build a reproduction container using the Dockerfile from the CI guide. Running tests inside this container matches the CI workflow and isolates the failure predictably.

Can I run CI workflow steps inside a Docker container to match the CI environment?

Yes, you can run CI workflow steps inside a Docker container to match the CI environment. Building a reproduction container using the project's CI guide Dockerfile allows you to run tests inside it and mirror the CI workflow exactly.