pipeline-diagnostics

Name: pipeline-diagnostics
Availability: InStock
Author: ethosengine

Diagnose Jenkins CI/CD pipeline failures by inspecting job status and build logs.

5|1|Updated Aug 14, 2025

Search Tags:#CI/CD #logs #pipeline #Jenkins #builds #diagnose

Ready to run

npx skills add https://github.com/ethosengine/elohim --skill pipeline-diagnostics

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps project teams identify and diagnose CI/CD pipeline failures in Jenkins-based pipelines, speeding up root-cause analysis and recovery.

Core Features & Use Cases

Jenkins status and build log analysis: Quickly retrieve job status, recent build results, and log excerpts to pinpoint failures.
Log pattern search and failure classification: Scan logs for error patterns and categorize failures (DNA, App, Seed, Deploy) to guide remediation.
Actionable guidance for remediation: Suggest concrete next steps, including checks for environment variables, configuration drift, and failing stages.
Use Case: When a build fails, run diagnostics to identify whether the issue is a code change, dependency, or deployment misconfiguration, then trigger targeted fixes.

Quick Start

Run mcp__jenkins__getStatus to verify overall health, then mcp__jenkins__getBuild with the target job to inspect recent failures and logs.

Frequently Asked Questions about pipeline-diagnostics

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

FAQPage Schema

How do I diagnose CI/CD pipeline failures in Jenkins?▼

Diagnose CI/CD pipeline failures by fetching Jenkins job status, inspecting recent build details, and searching logs for error patterns to identify root causes. The process categorizes failures and provides actionable remediation steps.

What causes Jenkins build failures during deployment?▼

Jenkins build failures stem from code changes, dependency issues, or deployment misconfigurations. Diagnostics scan logs to classify failures across orchestrator, app, edge, and deploy stages, checking for environment variable issues and configuration drift.

How do I search Jenkins build logs for specific error patterns?▼

Search Jenkins build logs for error patterns by retrieving job details and scanning log excerpts to pinpoint failures. The diagnostic process categorizes these failures to guide targeted remediation steps.

Does Jenkins pipeline diagnostics work for multi-stage workflows?▼

Jenkins pipeline diagnostics covers multi-stage workflows including orchestrator, holochain, edge, app, and genesis stages. It diagnoses build, deploy, and test failures across these stages to identify root causes.

What's the best way to identify root causes of failing Jenkins jobs?▼

The best way to identify root causes of failing Jenkins jobs is to retrieve overall health status, inspect recent build results, and search logs for classified error patterns to generate actionable remediation guidance.

Why does my Jenkins pipeline fail with configuration drift?▼

Jenkins pipeline failures from configuration drift occur when environment settings change unexpectedly. Diagnostics check environment variables and configuration consistency, then suggest concrete next steps to resolve the detected misconfiguration.