keel-ci-check

Automates CI status checks, analyzes failed jobs, and proposes fixes from logs and source code.

4|Updated May 23, 2026

Search Tags:#code analysis #CI/CD #failure analysis #CI #CI status

Ready to run

npx skills add https://github.com/berkayturanci/keel --skill keel-ci-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: keel-ci-check
Source: https://github.com/berkayturanci/keel/tree/main/.agents/skills/keel-ci-check
Command: npx skills add https://github.com/berkayturanci/keel --skill keel-ci-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of checking the latest CI run's status and provides a detailed analysis of failed jobs, including the root cause and a proposed fix.

Core Features & Use Cases

CI Status Check: Automatically retrieve and check the status of the latest CI run.
Failure Analysis: Diagnose the root cause of a failed job by analyzing logs and source code.
Fix Proposals: Propose specific fixes for the identified issues without automatically applying them.
Use Case: Integrate this Skill into your CI workflow to ensure smooth deployment processes and reduce the time spent on manual debugging.

Quick Start

Use the keel-ci-check skill to check the CI status of the current branch.

Frequently Asked Questions about keel-ci-check

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

FAQPage Schema

How do I automate CI failure analysis for failed jobs?▼

Automate CI failure analysis by retrieving the latest CI run status, diagnosing the root cause of failed jobs through log and source code analysis, and generating proposed fixes without automatically applying them.

Can I automatically check CI status and find the root cause of failures?▼

Yes, you can automatically check CI status by retrieving the latest run results and analyzing CI logs alongside source code to identify the root cause of failed jobs.

What is the best way to propose fixes for failed CI jobs?▼

The best way to propose fixes for failed CI jobs is to automate the diagnosis of the root cause from CI logs and source code, then generate specific fix proposals for developers to review.

Do I need access to CI logs and source code to analyze CI failures?▼

Yes, you need access to CI logs and source code to analyze CI failures, as diagnosing the root cause of a failed job requires examining both the execution logs and the relevant source code.

Does the CI failure analysis tool automatically apply fixes to the source code?▼

No, the CI failure analysis tool does not automatically apply fixes; it proposes specific fixes for the identified issues, allowing developers and CI/CD engineers to review and manually apply them.