skills.rest
zekiriabd
zekiriabdCOMMUNITY
Explore all skills by this author →
GitHub

debugging-failed-pipeline

Diagnose failed SDDPro pipelines by identifying blocking gates and verifying fixes.

140|20|Updated Jun 20, 2026
Search Tags:#test failures#build failures#pipeline debugging#diagnostic reports#error classification#sddpro#api gate
One-click install
npx skills add https://github.com/zekiriabd/SDD-Pro --skill debugging-failed-pipeline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging-failed-pipeline
Source: https://github.com/zekiriabd/SDD-Pro/tree/main/.sdd/skills/debugging-failed-pipeline
Command: npx skills add https://github.com/zekiriabd/SDD-Pro --skill debugging-failed-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature code changes when an SDDPro pipeline fails by identifying the blocking gate, reading its diagnostic report, and following the documented fix.

Core Features & Use Cases

  • Gate Identification: Determine whether the failure originated in the build, QA, API, specification, review, security, stack, or planning stage.
  • Report-Driven Diagnosis: Match error classes to the correct persisted report and use its cause and fix guidance.
  • Safe Verification: Re-run the failed workflow step and confirm the resulting verdict before declaring resolution.
  • Use Case: When an API Gate returns RED or coverage falls below its threshold, use this Skill to locate the relevant report, apply the prescribed corrective action, and verify the gate again.

Quick Start

Ask the debugging-failed-pipeline skill to investigate the failed SDDPro pipeline, identify its blocking gate, read the relevant report, and verify the fix.

Frequently Asked Questions about debugging-failed-pipeline

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

FAQPage Schema
How do I diagnose failed CI pipelines without prematurely changing code?▼

Pipeline debugging requires classifying the reported error to determine the blocked workflow stage, reading the relevant persisted report for cause and fix guidance, and rerunning the affected stage for evidence-based verification.

What is the best way to debug an API Gate RED result or coverage threshold failure?▼

The best way to debug an API Gate RED result is to locate the relevant persisted report, apply the prescribed corrective action, and verify the gate again by rerunning the failed workflow step.

Can I use diagnostic reports to fix SDDPro build and test failures?▼

Yes, you can use diagnostic reports to fix SDDPro build and test failures by matching error classes to the correct persisted report and applying its documented cause and fix guidance for resolution.

Why does my SDDPro pipeline fail during the specification, review, or planning stages?▼

SDDPro pipelines fail during specification, review, or planning stages due to security blocks or stale plans, requiring error classification and consultation of the matching status report to apply the documented fix.

Does SDDPro pipeline debugging support rerunning failed workflow stages for verification?▼

Yes, SDDPro pipeline debugging supports safe verification by rerunning the failed workflow step and confirming the resulting verdict before declaring the pipeline failure resolved.

Related Skills

Explore More Software Engineering Skills→
cardano-foundationcardano-foundation
822

debug

Diagnose Buildkite CI failures by listing builds, inspecting jobs, and fetching logs.

Official
Intermediate
apokamoapokamo
12

issue-verify-code

Verify code fixes against prior feedback and git diff HEAD~1.

Community
Intermediate
SkogAISkogAI
1

verification-before-completion

Run verification commands and report evidence before claiming completion.

Official
Basic
michael-frelingmichael-freling

ci-error-fix

Diagnoses CI pipeline build, lint, and test failures with iterative fixes and verification.

Community
Advanced