fix-ci

Diagnose and fix failed CI checks using annotations and check output.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill fix-ci-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-ci
Source: https://github.com/Tyrizx/Tyrizx/tree/main/src/vs/sessions/skills/fix-ci
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill fix-ci-tyrizx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a pull request's CI checks fail, developers must manually dig through check logs, annotations, and output to find root causes. This Skill automates that investigation and applies the necessary code fixes directly in the current session. ## Core Features & Use Cases - Failure Analysis: Reads failed check information including check name, status, conclusion, details URL, annotations, and output to identify root causes such as compile errors, lint violations, or failing tests. - Targeted Code Fixes: Makes the necessary code changes to resolve failures while avoiding unrelated modifications. - Local Validation: Verifies fixes locally where possible by compiling, linting, or running relevant tests. - Use Case: After opening a pull request, you click the Fix Checks button in the Changes toolbar, and the Skill inspects the failed checks, fixes a lint error and a broken test, then validates the changes. ## Quick Start Ask the assistant to fix the failed CI checks for this session using the attached check information.

Frequently Asked Questions about fix-ci

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

FAQPage Schema
How do I fix failed CI checks automatically?▼

Trigger the Fix Checks button in the Changes toolbar, which provides the failed check information to the Skill. It reads annotations and check output, identifies root causes, and makes the necessary code changes to resolve the failures.

What types of CI failures can be diagnosed from check output?▼

The Skill handles common failure categories including compile errors, lint and hygiene violations, and failing tests. It uses the annotations and output attached to each failed check to pinpoint the root cause before editing code.

Does the fix-ci skill make unrelated code changes?▼

No. The Skill is instructed to focus on resolving the CI failures and avoid unrelated changes unless they are required to fix the checks. This keeps the resulting diff scoped to the failing checks.

Can CI fixes be validated before pushing?▼

Yes. The workflow includes a local validation step where changes are verified by compiling, linting, or running the relevant tests where possible, confirming the failures are addressed before completion.

What information is needed to diagnose a failed check?▼

The Skill needs the failed check details attached to the message: a pull request link, and for each failed check the name, status, conclusion, details URL, plus any annotations or output. Without this context, root cause analysis is limited.