skills.rest
thisrohangupta
thisrohanguptaCOMMUNITY
Explore all skills by this author →
Website𝕏@ThisRohanGuptaGitHub

debug-pipeline

Diagnose Harness pipeline execution failures by analyzing stages, steps, timing, and logs.

1|Updated Apr 16, 2026
Search Tags:#CI/CD#diagnosis#pipeline debugging#Harness#execution analysis
One-click install
npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill debug-pipeline-thisrohangupta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-pipeline
Source: https://github.com/thisrohangupta/cursor-harness-plugin/tree/main/skills/debug-pipeline
Command: npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill debug-pipeline-thisrohangupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires harness-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The debug-pipeline skill helps users quickly diagnose and understand the root causes of Harness pipeline failures.

Core Features & Use Cases

  • Diagnose Failures: Analyze both successful and failed executions to provide detailed reports.
  • Detailed Reports: Break down stages, steps, timing, bottlenecks, and failure details.
  • Use Case: When you need to debug a pipeline failure, find out why a build failed, or analyze pipeline errors, this skill can help you identify the problem quickly.

Quick Start

Diagnose the execution with the ID 'abc123' using the command 'debug pipeline execution abc123'.

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 Harness pipeline failure using an execution ID?▼

To debug a Harness pipeline failure, provide the execution ID to diagnose root causes by analyzing stages, steps, timing, and logs. This generates a detailed breakdown report of the failure.

What is pipeline execution analysis in CI/CD and when do I need it?▼

Pipeline execution analysis in CI/CD identifies root causes of failures by examining stages, steps, and timing. You need it when a build fails or when diagnosing pipeline performance bottlenecks.

Do I need the Harness CLI to analyze pipeline execution details?▼

Yes, analyzing pipeline execution details requires the harness-cli dependency and access to the Harness MCP v2 server to retrieve the logs and step data needed for diagnosis.

Can I diagnose bottlenecks and analyze timing in successful Harness pipeline executions?▼

Yes, you can diagnose both successful and failed Harness pipeline executions. The analysis breaks down step timing and stage details to identify bottlenecks and provide performance insights.

What's the best way to find out why my CI/CD build failed in Harness?▼

The best way to find out why a CI/CD build failed is to run an execution diagnosis, which analyzes execution logs and step details to pinpoint the exact failure point and root cause.

Related Skills

Explore More Software Engineering Skills→
thisrohanguptathisrohangupta
1

create-pipeline-v1

Generate Harness v1 Pipeline YAML with Python scripts and MCP v2 server.

Community
Advanced
TalonT-OrgTalonT-Org
5

diagnose-ci

Fetch CI logs for a failing Git branch and classify failure types.

Official
Intermediate
Arvo-AIArvo-AI
387

spinnaker

Correlate Spinnaker pipeline executions with application health and logs for RCA.

Official
Advanced
zm2231zm2231

ci-cd-helper

Diagnose build failures and optimize CI/CD pipelines for GitHub Actions and Kubernetes.

Community
Advanced