A command for investigating failed continuous-integration jobs. Continuous integration, or CI, automatically builds and tests code whenever changes are submitted.

Use it to inspect a job or failure category, analyze logs and stack traces, find trends, assess impact, and prioritize fixes.

It goes beyond listing failures by looking for root causes, repeated or flaky failures, relationships between jobs, and whether the problem is infrastructure or code.

ci-triage — Command for Claude Code by lyarwood

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/lyarwood/kubevirt-ai-helpers

Made for: Claude Code.

Or install kubevirt, the plugin that ships this one along with the rest of its 4 skills, 17 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-triage/github.svg)](https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-triage)

Your own site

<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-triage"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-triage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lyarwood/kubevirt-ai-helpers/ci-triage"><img src="https://agentmods.dev/badge/commands/lyarwood/kubevirt-ai-helpers/ci-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,938 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.01938
Opus 5	$0.00006	$0.00969
Sonnet 5	$0.00003	$0.00388
Haiku 4.5	$0.00001	$0.00194

Measured 12d ago against content hash 955be923e4cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ci-triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/kubevirt/commands/ci-triage.md · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

kubevirt:ci-triage

Synopsis

/kubevirt:ci-triage <job-or-category> [--context <context>] [--deep-analysis]

Description

The kubevirt:ci-triage command performs intelligent CI failure triage using AI-powered analysis capabilities from the healthcheck MCP server. It goes beyond simple failure counting to provide root cause analysis, impact assessment, and prioritized recommendations for addressing CI failures.

This command leverages multiple healthcheck MCP tools to:

Fetch comprehensive failure data for the target job or category
Analyze failure trends and detect flakiness patterns
Perform cross-job correlation to identify systemic issues
Assess business impact based on context (production, development, pre-release)
Generate prioritized triage recommendations with resource allocation guidance

Advanced Analysis Features

Root Cause Analysis

Parse failure logs and stack traces
Identify common error patterns
Distinguish infrastructure vs code issues
Extract file locations and error messages
Generate GitHub URLs for source code review

Trend & Flakiness Detection

Historical trend analysis (improving, stable, degrading)
Flakiness scoring (10-90% failure rate patterns)
Frequency analysis over time
Regression detection

Cross-Job Correlation

Identify failures affecting multiple jobs
Environment-specific patterns (ARM64 vs x86)
Kubernetes version correlation
Resource issue detection (CPU, memory, disk)

Impact Assessment

Context-aware prioritization (production vs development)
Business impact scoring (critical path vs edge cases)
Urgency classification (urgent, normal, low)
Resource allocation recommendations (senior engineer vs standard triage)

Quarantine Intelligence

Effectiveness scoring for current quarantines
Recommendations for quarantine decisions (add, remove, extend)
Active vs stale quarantine identification
CI health impact analysis

Implementation

Phase 1: Data Collection

Determine target scope (specific job or category)

Fetch failure data using appropriate healthcheck command:

# For specific job
healthcheck lane <job-name> --since 7d --output json

# For category
healthcheck merge <category> --output json

Parse JSON output for baseline analysis

Read the full file on GitHub · 239 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 239 lines · 13 tokens per session scan A 955be923e4cd

Subscribe to this mod's changes

ci-triage is a command published in the GitHub repository lyarwood/kubevirt-ai-helpers (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,938 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

CI and CD Debugging DevOps and cloud

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

ci-triage