debug-pipeline

Diagnose OpenShift Pipelines (Tekton) failures by analyzing PipelineRun status and TaskRun logs.

48|31|Updated Feb 2, 2026

Search Tags:#CI/CD #OpenShift #pipeline debugging #Tekton #taskrun analysis

Ready to run

npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-pipeline-rhecosystemappeng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-pipeline
Source: https://github.com/RHEcosystemAppEng/agentic-plugins/tree/main/rh-developer/skills/debug-pipeline
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-pipeline-rhecosystemappeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oc, tkn, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of diagnosing and troubleshooting OpenShift Pipelines (Tekton) failures, including PipelineRun failures, TaskRun errors, workspace/PVC issues, and authentication problems.

Core Features & Use Cases

Automated PipelineRun Status: Gathers PipelineRun status, failed TaskRun details, and related resource checks.
TaskRun Analysis: Provides detailed analysis of failed TaskRun steps, including container logs and workspace bindings.
Resource Checks: Validates ServiceAccounts, Workspaces/PVCs, Secrets, and Pipeline/Task Definitions.
Use Case: When an OpenShift Pipeline (Tekton) encounters failures, hangs, or produces unexpected results, this Skill automates the diagnosis process.

Quick Start

To diagnose a PipelineRun failure, use the command: /debug-pipeline

Frequently Asked Questions about debug-pipeline

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

FAQPage Schema

How do I debug a failed OpenShift PipelineRun in Tekton?▼

Debugging a failed Tekton PipelineRun involves analyzing PipelineRun status, failed TaskRun details, and step container logs to pinpoint errors. Automating this diagnosis extracts failure points from TaskRun steps and related resources to identify the root cause quickly.

Why does my Tekton TaskRun fail with workspace or PVC binding errors?▼

Tekton TaskRun failures with workspace or PVC binding errors occur when volume configurations are mismatched or unavailable. Analyzing the TaskRun details and workspace bindings validates the PVC configurations and extracts the exact step container logs causing the failure.

Do I need oc and tkn CLI tools to diagnose OpenShift Pipeline failures?▼

Yes, you need the oc and tkn CLI tools installed to diagnose OpenShift Pipeline failures. These dependencies provide the command-line access required to query PipelineRun status, TaskRun logs, and validate cluster resources like Secrets and ServiceAccounts.

Can I troubleshoot authentication problems in Tekton CI/CD pipelines automatically?▼

Yes, you can troubleshoot authentication problems in Tekton CI/CD pipelines automatically by validating ServiceAccounts and Secrets. The diagnosis process checks these related resources against the PipelineRun definitions to identify misconfigured credentials or missing access rights.

What is the best way to analyze step container logs for a stuck PipelineRun?▼

The best way to analyze step container logs for a stuck PipelineRun is to gather the failed TaskRun details and extract the specific step outputs. Automating this log collection across the Tekton pipeline identifies hang points and unexpected execution results.