diagnose-ci-failures

Collect GitHub Actions status checks and logs to outline fixes for CI failures.

Updated Apr 30, 2026

Search Tags:#planning #logs #github #diagnosis #ci #pull-request

Ready to run

npx skills add https://github.com/lalaABC/waprcn --skill diagnose-ci-failures-lalaabc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose-ci-failures
Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/diagnose-ci-failures
Command: npx skills add https://github.com/lalaABC/waprcn --skill diagnose-ci-failures-lalaabc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose CI failures for a PR by collecting status checks and relevant logs and summarizing actionable fixes.

Core Features & Use Cases

Deterministic workflow to check CI status, extract failure logs, analyze errors, and create a plan (not code changes) to resolve issues.
Categorizes errors by type: formatting, linting, compilation, test failures, and platform-specific issues.
Use Case: When a PR build fails, generate a concrete plan outlining steps to fix issues before merging.

Quick Start

Invoke this skill on the active PR to generate a concise CI-fix plan.

Frequently Asked Questions about diagnose-ci-failures

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

FAQPage Schema

How do I diagnose CI failures for a pull request?▼

To diagnose CI failures for a pull request, you need to collect status checks and extract relevant logs from your GitHub workflows. This process involves analyzing the errors and generating an actionable plan to resolve the build failures before merging.

How do I triage test failures and investigate PR build failures across GitHub workflows?▼

Triage test failures by pulling CI issues and collecting run logs from GitHub workflows. You can investigate PR build failures by categorizing the extracted errors into formatting, linting, compilation, test failures, or platform-specific issues to understand the root cause.

Do I need the GitHub CLI to extract failure logs and check CI status?▼

Yes, diagnosing CI failures requires the GitHub CLI (gh) and access to pr view and run view commands. These CLI commands are necessary to collect status checks and pull relevant logs to outline actionable fixes for your pull request.

Can I automatically apply code changes to resolve CI issues?▼

No, diagnosing CI failures generates a concrete plan document outlining steps to fix issues without applying code changes. It provides a deterministic workflow to analyze errors and summarize actionable fixes that you must implement manually.

What types of CI errors can be categorized when checking CI status?▼

When checking CI status, errors can be categorized by type including formatting, linting, compilation, test failures, and platform-specific issues. This categorization helps outline actionable fixes for resolving PR build failures across GitHub workflows.