ci-fix

Diagnose GitHub Actions CI failures and push minimal fixes to a dedicated branch.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/jaypatrick/skills --skill ci-fix-jaypatrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-fix
Source: https://github.com/jaypatrick/skills/tree/main/ci-fix
Command: npx skills add https://github.com/jaypatrick/skills --skill ci-fix-jaypatrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix GitHub Actions CI failures by inspecting workflow runs and logs, identifying root causes, implementing minimal diffs, and pushing fixes to a dedicated fix branch.

Core Features & Use Cases

  • Locate the failing run and identify the responsible job or step across PR or branch builds.
  • Extract failure logs and artifacts to pinpoint root causes, including common build, test, lint, or environment issues.
  • Apply minimal, scoped fixes that preserve existing workflows and permissions, avoiding broad changes.
  • Push fixes to a dedicated branch (ci-fix/<original-branch>) and push for verification.
  • Verify the fix by triggering CI on the fix branch and confirming green status.

Quick Start

Provide a failing workflow run identifier and follow prompts to locate failures, apply a minimal fix, and push to a dedicated fix branch.

Frequently Asked Questions about ci-fix

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

FAQPage Schema
How do I automatically diagnose GitHub Actions CI failures and implement fixes?

You can automatically diagnose GitHub Actions CI failures by inspecting workflow runs and logs, pinpointing root causes, and pushing minimal fixes to a dedicated branch. This process requires gh CLI authentication and repository access.

What is the best way to fix failing CI pipelines without opening a pull request?

The best way to fix failing CI pipelines without opening a pull request is to push minimal, scoped fixes directly to a dedicated ci-fix branch for verification, which avoids broad workflow changes and PR overhead.

Do I need gh CLI authentication to troubleshoot GitHub Actions workflow logs?

Yes, you need gh CLI authentication and repository access to troubleshoot GitHub Actions workflow logs. This allows the diagnostic process to locate failing runs and extract failure logs to identify root causes.

Can I apply minimal diffs to fix CI build and test failures across branch builds?

Yes, you can apply minimal diffs to fix CI build and test failures across branch builds. This approach preserves existing workflows and permissions while pushing targeted fixes to a dedicated branch for verification.

How does root cause analysis work for GitHub Actions environment and lint issues?

Root cause analysis for GitHub Actions environment and lint issues works by extracting failure logs and artifacts from the failing job or step, pinpointing the exact error, and implementing a minimal, scoped fix to resolve it.

What are the limitations of automated CI failure resolution for branch builds?

A limitation of automated CI failure resolution is that fixes are pushed only to a dedicated ci-fix branch without opening PRs, requiring separate manual intervention to merge the verified fixes back into the original branch.