ci-triage

Name: ci-triage
Availability: InStock
Author: ethosengine

Diagnose CI/CD failures by analyzing ci-summary.json build artifacts.

5|1|Updated Aug 14, 2025

Search Tags:#CI/CD #patterns #diagnostics #root-cause #artifact-analysis #ci-triage #build-failure

Ready to run

npx skills add https://github.com/ethosengine/elohim --skill ci-triage

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick CI/CD failure diagnosis to accelerate debugging and reduce MTTR when builds fail.

Core Features & Use Cases

Guided triage: Step-by-step workflow to identify root causes in CI pipelines.
Targeted searches: Category-specific patterns to narrow down issues quickly.
Artifact-based analysis: Fetches and analyzes ci-summary.json artifacts for fast remediation.
Use Case: When a build fails after merging, run this Skill to locate common failure points and propose fixes.

Quick Start

Use the ci-triage skill to inspect a failing elohim orchestrator build and fetch the ci-summary.json artifact.

Frequently Asked Questions about ci-triage

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

FAQPage Schema

How do I diagnose a CI/CD build failure and find the root cause quickly?▼

To diagnose a CI/CD build failure, you can use guided triage workflows that apply category-specific search patterns and analyze build artifacts to surface actionable root-cause insights.

How do I use build artifacts like ci-summary.json to troubleshoot a failing pipeline?▼

Build artifacts like ci-summary.json are fetched and analyzed to reproduce issues and guide remediation, providing deterministic data access to identify common failure points in your pipeline.

What is the best way to reduce MTTR when a CI pipeline breaks after merging code?▼

To reduce MTTR for broken CI pipelines, apply targeted artifact-based analysis and category-specific search patterns that quickly narrow down failure points and propose actionable fixes.

Can I use category-specific search patterns to narrow down CI failure diagnostics?▼

Yes, applying category-specific search patterns during triage narrows down CI failure diagnostics by directing the investigation toward specific build issue categories and artifact data.

Does this CI triage approach require specific dependencies to analyze failing builds?▼

No specific dependencies are required for this CI triage approach; it relies on deterministic steps and artifact-based data access to reproduce issues across failing CI pipelines.

When should I not use artifact-based analysis for CI failure triage?▼

You should avoid artifact-based CI failure triage when build artifacts like ci-summary.json are unavailable, as the process depends on fetching these artifacts to reproduce issues and guide remediation.