skills.rest
zpoint
zpointCOMMUNITY
Explore all skills by this author →
GitHub

debug-ci

Trace CI test failures to root causes and enforce design fixes.

40|8|Updated May 14, 2026
Search Tags:#root cause analysis#github actions#e2e testing#test failure#agent debugging#ci debugging#design fixes
One-click install
npx skills add https://github.com/zpoint/vibe-seller --skill debug-ci-zpoint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-ci
Source: https://github.com/zpoint/vibe-seller/tree/main/.claude/skills/debug-ci
Command: npx skills add https://github.com/zpoint/vibe-seller --skill debug-ci-zpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI test failures are often incorrectly dismissed as flaky, unrelated to current changes, or resolved with temporary workarounds that mask underlying design flaws and cause recurring issues. This Skill enforces a rigorous root cause analysis process to identify and fix the actual source of failures, preventing wasted effort and unstable codebases.

Core Features & Use Cases

  • Mandatory Artifact Log Analysis: Requires downloading and reviewing server logs, agent debug events, and API call traces instead of relying solely on limited test output.
  • Structured Root Cause Tracing: Provides step-by-step guidance to trace agent behavior, test logic, and system state transitions to pinpoint the exact source of failures.
  • Design-First Fix Enforcement: Mandates fixing underlying architectural or design flaws instead of applying symptom-level workarounds like retries or loosened assertions.
  • Use Case: For example, when an end-to-end test for a cross-border e-commerce browser automation agent fails intermittently, use this Skill to trace the agent's tool calls and task state transitions to identify a race condition in the task scheduling system, then fix the state machine to eliminate the bug class entirely.

Quick Start

Use the debug-ci skill to investigate the latest failing CI run for the vibe-seller repository, identify the root cause of the e2e test failure, and propose a permanent design-level fix that prevents the bug from recurring.

Frequently Asked Questions about debug-ci

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

FAQPage Schema
How do I find the root cause of intermittent GitHub Actions test failures?▼

Trace GitHub Actions test failures to the root cause by downloading and reviewing server logs, agent debug events, and API call traces to pinpoint exact state transition bugs instead of dismissing them as flaky.

Why do my e2e browser automation tests fail intermittently and how to stop it?▼

End-to-end browser automation tests fail intermittently due to underlying design flaws like race conditions in task scheduling. Trace agent tool calls and state transitions to find the exact source and apply a design-level fix to eliminate the bug class.

What is the best way to debug cross-platform integration test failures in CI?▼

The best way to debug cross-platform integration test failures is enforcing a structured root cause analysis process that mandates artifact log review and code invariant enforcement to produce permanent design fixes rather than temporary symptom-level workarounds.

Does this CI debugging approach work with agent task tests?▼

Yes, this CI debugging approach works with agent task tests by tracing agent behavior, test logic, and system state transitions to pinpoint the exact source of failures and mandate architectural fixes that prevent bug recurrence.

When should I not use retries to fix flaky CI tests?▼

You should not use retries to fix flaky CI tests when the failure stems from an underlying architectural or design flaw, as symptom-level workarounds like retries or loosened assertions mask the root cause and lead to recurring issues.

Related Skills

Explore More Software Engineering Skills→
linfordWulinfordWu
1

root-cause-localization

Identify root-cause components from logs and traces within a fault window.

Community
Advanced
a29paula29paul
1

gstack-openclaw-investigate

Enforce root cause investigation before bug fixes in software debugging workflows.

Community
Advanced
devopstalesdevopstales
1

playwright

Automate Playwright browser tests and capture screenshots and traces.

Community
Intermediate
tonone-aitonone-ai
69

vigil-incident

Diagnose production incidents by analyzing logs, metrics, and traces to identify root cause.

Official
Advanced