jenkins-debug

Diagnose Jenkins deployment failures by reading tunnel logs and reporting root causes.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill jenkins-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jenkins-debug
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/jenkins-debug
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill jenkins-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly diagnose why a Skaile deployment failed on Jenkins by reading the local Jenkins tunnel, locating the failing build, and presenting a structured summary with a suggested fix hypothesis.

Core Features & Use Cases

  • Read-only Jenkins diagnostics: determine why a deployment failed without triggering builds or modifying Jenkins.
  • Failure-region extraction: parse the console log to identify the exact stage and error region.
  • Cross-reference commits: correlate recent skaile-dev commits around the build timestamp to surface potential root causes.

Quick Start

Describe the Jenkins failure scenario to generate a diagnostic report.

Frequently Asked Questions about jenkins-debug

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

FAQPage Schema
How do I debug a Jenkins deployment failure without triggering a new build?

You can debug a Jenkins deployment failure by using anonymous read-only access to fetch console logs and metadata, extracting the failure region, and generating a markdown report without modifying Jenkins.

What is the best way to find the root cause of a CI deployment failure from console logs?

Finding the root cause of a CI deployment failure involves parsing Jenkins console logs to identify the exact failing stage, then cross-referencing recent commits around the build timestamp to surface potential triggers.

Can I read Jenkins logs locally if I only have anonymous read-only API access?

Yes, you can read Jenkins logs locally through a Jenkins tunnel using anonymous read-only API access to locate the failing build and extract diagnostic metadata safely.

How do I cross-reference recent commits with a failing Jenkins build to find what broke the deployment?

To cross-reference recent commits with a failing Jenkins build, you correlate commit timestamps around the build time with the extracted error region from the console logs to produce a fix hypothesis.

Does this Jenkins diagnostic approach work for any CI pipeline or only specific deployments?

This diagnostic approach specifically applies to debugging the skaile_platform and skaile_store deployments, targeting their Jenkins CI pipelines rather than supporting arbitrary pipeline configurations.

What should I do when Jenkins deployment logs are too long to manually locate the failure region?

When Jenkins deployment logs are too long, you can programmatically parse the console output to extract the exact failure region and stage, then receive a structured markdown summary for actionable fixes.