ci

Name: ci
Availability: InStock
Author: Envio

Fetch failed GitHub Actions workflow logs and diagnose CI failures.

541|54|Updated May 24, 2024

Search Tags:#automation #debugging #logs #github-actions #ci-cd #ci

Ready to run

npx skills add https://github.com/enviodev/hyperindex --skill ci-enviodev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/enviodev/hyperindex/tree/main/.claude/skills/ci
Command: npx skills add https://github.com/enviodev/hyperindex --skill ci-enviodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly diagnose CI failures by fetching the latest failed workflow run for the current branch or pull request and exposing the associated job logs.

Core Features & Use Cases

Retrieve the most recent failed GitHub Actions run for the active branch or PR.
List each failed job with status and identifiers to pinpoint where to focus.
Retrieve and inspect logs for failed jobs, with guidance for using gh when available or falling back to WebFetch.
Check for annotations and provide a concise diagnosis to surface common root causes and flaky builds.

Quick Start

Run this skill in your repository to fetch the latest failed workflow run for the current branch or PR and display the corresponding job logs.

Frequently Asked Questions about ci

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

FAQPage Schema

How do I diagnose GitHub Actions CI failures from logs on a pull request?▼

To diagnose GitHub Actions CI failures, this skill fetches the latest failed workflow run for the current branch or PR and surfaces the corresponding job logs. It identifies failed jobs and checks annotations to pinpoint root causes for rapid debugging.

What is the best way to fetch failed workflow run logs for a feature branch?▼

The best way to fetch failed workflow logs is using the gh CLI when available to retrieve job outputs for the active branch. This skill falls back to WebFetch if gh is absent, parsing the results with Python to expose the relevant CI failure data.

Does this CI debugging skill require any specific tools or dependencies installed?▼

Yes, diagnosing CI failures requires curl and Python to be installed for fetching and parsing workflow results. The skill also leverages the gh CLI to retrieve logs and annotations if it is available in your current environment.

Can I use this skill to identify flaky builds in GitHub Actions?▼

Yes, you can identify flaky builds because the skill retrieves annotations and provides a concise diagnosis for the latest failed workflow run. It surfaces common root causes associated with the failed job logs on your feature branch or PR.

Why does my GitHub Actions workflow fail and how do I pinpoint the failing job?▼

Your GitHub Actions workflow might fail due to various build or test errors. This skill lists each failed job with its status and identifiers, retrieves the associated logs, and checks annotations to pinpoint exactly where you should focus your debugging.

How do I retrieve GitHub Actions annotations to understand CI failure root causes?▼

To retrieve GitHub Actions annotations, this skill uses the gh CLI or WebFetch to check the latest failed workflow run. It then parses the logs and annotations using Python to provide a concise diagnosis of common root causes.