ci-fix

Diagnose GitHub Actions CI failures from run URLs and propose fixes.

Updated Feb 23, 2026

Search Tags:#automation #debugging #logs #github-actions #root-cause #ci

Ready to run

npx skills add https://github.com/dwertent/.cursor --skill ci-fix-dwertent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-fix
Source: https://github.com/dwertent/.cursor/tree/main/skills/ci-fix
Command: npx skills add https://github.com/dwertent/.cursor --skill ci-fix-dwertent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix CI workflow failures from GitHub Actions run links by analyzing run data and logs to quickly identify the root cause.

Core Features & Use Cases

Parse a GitHub Actions run URL to extract run and job identifiers.
Retrieve run details and failure logs to pinpoint the first failure.
Propose and, where possible, apply fixes locally, or generate a remediation plan with a summarized report.

Quick Start

Provide a GitHub Actions run URL to have the system diagnose and propose fixes for the failing workflow.

Frequently Asked Questions about ci-fix

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

FAQPage Schema

How do I diagnose and fix GitHub Actions CI failures from a run URL?▼

To diagnose GitHub Actions CI failures, provide the run URL so the system can parse the identifiers, retrieve the logs, pinpoint the root cause, and propose or apply fixes. This process generates a summarized remediation report for the failing workflow.

Can I automatically find the root cause of a CI workflow failure from logs?▼

Yes, you can automatically identify the root cause of CI workflow failures by analyzing run data and logs. The system pinpoints the first failure within the GitHub Actions job logs to guide the necessary fixes for build, test, lint, or infrastructure issues.

What types of CI failures can be analyzed using a GitHub Actions run link?▼

Build, test, lint, and infrastructure failures across repositories can be analyzed using a GitHub Actions run link. The system examines job conclusions and failure logs to propose fixes for the identified workflow issues.

Does this CI debugging process work for any GitHub repository?▼

Yes, the CI debugging process applies to GitHub Actions workflow failures across repositories. By parsing run and job identifiers from the provided URL, it retrieves details and proposes fixes regardless of the specific repository.

What is the best way to troubleshoot failing GitHub Actions jobs?▼

The best way to troubleshoot failing GitHub Actions jobs is to parse the run URL to extract identifiers, retrieve the failure logs, and identify the root cause. This approach guides fixes and generates a deliverable remediation plan.