ci-fix

Diagnose failing CI builds, apply fixes, and open a pull request.

30|5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/max-sixty/tend --skill ci-fix-max-sixty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-fix
Source: https://github.com/max-sixty/tend/tree/main/plugins/tend-ci-runner/skills/ci-fix
Command: npx skills add https://github.com/max-sixty/tend --skill ci-fix-max-sixty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug and fix failing CI builds on the default branch by diagnosing root causes, applying targeted fixes, and opening a pull request.

Core Features & Use Cases

  • Automated failure analysis: Inspects CI logs to identify the root cause and relevant files.
  • Reproducible fixes: Guides local reproduction and validation before commit.
  • PR-driven workflow: Creates a structured PR with context and testing notes to merge the fix.

Quick Start

Run the fix workflow against a failing CI run to generate a PR that addresses the root cause.

Frequently Asked Questions about ci-fix

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

FAQPage Schema
How do I automatically fix a failing CI build on my main branch?

To fix a failing CI build on your default branch, this skill inspects CI logs to perform root-cause analysis, applies targeted cross-file code changes, and opens a pull request with the verified fix.

What is the best way to debug continuous integration failures and create a pull request?

Debugging continuous integration failures involves structured log inspection and root-cause analysis. This skill automates that workflow by guiding local reproduction, applying code changes, and creating a PR with context and testing notes.

Can I automate GitHub pull request creation after diagnosing a build failure?

Yes, you can automate GitHub pull request creation after diagnosing a build failure. This skill enforces a PR-driven workflow that packages the cross-file code fixes and testing notes into a structured pull request.

Does automated CI failure diagnosis work for projects requiring cross-file code changes?

Automated CI failure diagnosis works for projects requiring cross-file code changes by inspecting logs to identify relevant files, guiding local validation before commit, and submitting a structured pull request to merge the fix.

Why use an automated workflow for continuous integration build failures instead of manual debugging?

An automated workflow for continuous integration build failures ensures reproducible fixes by enforcing a structured process from failure identification through fix verification, reducing the manual effort needed for log inspection and root-cause analysis.