ci-job-analysis

Classify CI job failures into types and generate remediation guidance.

2|Updated Nov 26, 2025

Search Tags:#automation #workflow #debugging #ci #stack-trace #failure-analysis

Ready to run

npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill ci-job-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-job-analysis
Source: https://github.com/penkzhou/swiss-army-knife-plugin/tree/main/swiss-army-knife/skills/ci-job-analysis
Command: npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill ci-job-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze CI job failures to classify issues and surface actionable remediation.

Core Features & Use Cases

Failure type taxonomy covering test_failure, e2e_failure, build_failure, lint_failure, type_check_failure, dependency_failure, config_failure, infrastructure_failure.
Confidence scoring, root-cause analysis, and a historical case-matching framework to prioritize fixes.
Tech stack recognition to distinguish frontend, backend, and mixed environments, with guidance for cross-stack failures.

Quick Start

Load the CI failure report and apply the standard remediation workflow to identify the root cause and recommended fixes.

Frequently Asked Questions about ci-job-analysis

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

FAQPage Schema

How do I analyze CI job failures to identify root causes?▼

To analyze CI job failures, you provide failure signals, file paths, error messages, and stack traces to classify the issue type and map it to a repair workflow. The analysis estimates confidence, identifies root causes, and references a historical case base for similarity scoring to produce remediation guidance.

What types of CI failures can be classified automatically?▼

CI failures can be classified into test_failure, e2e_failure, build_failure, lint_failure, type_check_failure, dependency_failure, config_failure, and infrastructure_failure. The taxonomy covers diverse pipeline issues, distinguishing frontend, backend, and mixed tech stack environments to surface appropriate remediation.

How do I fix e2e or test failures using stack traces?▼

Fixing e2e or test failures involves loading stack traces and error messages to apply a structured remediation workflow. The process identifies root causes, estimates confidence, and scores against a historical case base to generate precise, actionable repair guidance.

What inputs are needed to debug CI build and lint failures?▼

Debugging CI build and lint failures requires failure signals, relevant file paths, error messages, stack traces, and environment context. Providing these inputs allows the analysis framework to accurately classify the failure type and map it to the appropriate repair workflow.

Can I use historical case matching for CI failure analysis?▼

Yes, historical case matching is used for CI failure analysis by scoring similarity against past cases. This framework helps prioritize fixes by estimating confidence and mapping the current failure to established repair workflows, improving remediation accuracy.

How does cross-stack failure analysis handle frontend and backend issues?▼

Cross-stack failure analysis recognizes tech stack environments to distinguish frontend, backend, and mixed issues. By evaluating failure signals and environment context, it maps complex cross-stack failures to appropriate repair workflows, ensuring precise remediation guidance.