skills.rest
TalonT-Org
TalonT-OrgOFFICIAL
Explore all skills by this author →
GitHub

diagnose-ci

Fetch CI logs for a failing Git branch and classify failure types.

5|1|Updated Feb 18, 2026
Search Tags:#automation#debugging#logs#github actions#failure analysis#ci
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill diagnose-ci
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose-ci
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/diagnose-ci
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill diagnose-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of investigating Continuous Integration (CI) failures by fetching relevant logs, classifying the error type, and generating a structured diagnosis report.

Core Features & Use Cases

  • Automated Log Fetching: Retrieves CI logs from failing branches using the GitHub CLI.
  • Failure Classification: Categorizes failures into types like test, lint, build, type_check, env, or unknown.
  • Fixability Assessment: Determines if a failure is likely fixable.
  • Use Case: When a CI pipeline fails on a pull request, this Skill can automatically gather the necessary information, classify the root cause, and provide a concise report, speeding up the debugging process.

Quick Start

Use the diagnose-ci skill to investigate CI failures on the 'main' branch.

Frequently Asked Questions about diagnose-ci

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

FAQPage Schema
How do I diagnose CI failures on a failing Git branch?▼

To diagnose CI failures, this Skill fetches logs from the failing Git branch, classifies the error type into categories like test or build, and generates a structured diagnosis report to speed up debugging.

What types of CI pipeline errors can be classified automatically?▼

CI pipeline errors are automatically classified into predefined categories including test, lint, build, type_check, env, or unknown, determining if the failure is likely fixable.

Do I need the GitHub CLI to fetch logs for failure analysis?▼

Yes, you need the GitHub CLI installed because the automated failure analysis relies on it to retrieve CI logs from failing branches before classifying the errors and generating a report.

Can I use this to investigate GitHub Actions failures on a pull request?▼

Yes, you can use it to investigate GitHub Actions failures on a pull request by automatically gathering the necessary CI logs, classifying the root cause, and providing a concise diagnosis.

What's the best way to automate CI/CD pipeline monitoring and failure analysis?▼

Automating CI/CD pipeline monitoring is achieved by fetching CI logs via GitHub CLI, categorizing failures into types like env or type_check, and generating a structured diagnosis report instantly.

Related Skills

Explore More Software Engineering Skills→
gqf2008gqf2008

github-auth

Authenticate Hermes Agent with GitHub via gh CLI or git tokens and SSH keys.

Community
Intermediate
barikata1984barikata1984

quality-review

Automates git-based code quality reviews for commits and pull requests.

Community
Intermediate
gniazdowski-lukgniazdowski-luk

static-code-analysis-typescript

Configure ESLint, Prettier, and GitHub Actions for TypeScript static analysis.

Community
Advanced
majedsiefalnasrmajedsiefalnasr

gh-fix-ci

Diagnose and fix failing GitHub Actions PR checks using gh CLI commands.

Community
Intermediate