ci-retry

Retry failed GitLab CI pipelines and Tekton PipelineRuns.

2|Updated Feb 16, 2026

Search Tags:#automation #pipeline #gitlab #retry #ci #tekton

One-click install

npx skills add https://github.com/dmzoneill/skills --skill ci-retry

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ci-retry
Source: https://github.com/dmzoneill/skills/tree/main/ci-retry
Command: npx skills add https://github.com/dmzoneill/skills --skill ci-retry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of retrying failed Continuous Integration (CI) pipelines, saving developers time and effort in re-running builds and tests.

Core Features & Use Cases

GitLab CI Retry: Retries specific failed jobs within a GitLab CI pipeline.
Konflux/Tekton Retry: Re-triggers failed Tekton PipelineRuns.
Automated Detection: Identifies the CI system (GitLab or Tekton) based on provided inputs.
Use Case: When a GitLab CI pipeline fails due to a transient issue, you can use this Skill to automatically retry the failed jobs without manual intervention.

Quick Start

Use the ci-retry skill to retry the pipeline for merge request !1234 in the automation-analytics/automation-analytics-backend project.

Frequently Asked Questions about ci-retry

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

FAQPage Schema

How do I retry a failed GitLab CI pipeline for a specific merge request?▼

Retry a failed GitLab CI pipeline by providing the MR ID and project name to an automation tool, which automatically identifies and re-triggers the failed jobs without requiring manual intervention through the web interface.

Can I re-trigger a failed Tekton PipelineRun automatically?▼

Yes, you can automatically re-trigger a failed Tekton PipelineRun by supplying the PipelineRun name to an automation tool, which executes the retry command and manages common errors like network issues or authorization problems.

How does automated CI retry handle network issues or authorization errors?▼

Automated CI retry handles network issues and authorization errors by embedding specific logic that detects these common failures during command execution, preventing silent crashes and surfacing the underlying problem for troubleshooting.

Does the CI retry approach work for both GitLab CI and Konflux systems?▼

Yes, the CI retry approach supports both GitLab CI and Konflux/Tekton systems by using automated detection logic to determine the target CI system based on the inputs provided, such as MR IDs or PipelineRun names.

What inputs do I need to retry a failed pipeline in GitLab or Tekton?▼

To retry a failed pipeline in GitLab, you need the project name and either the MR ID or pipeline ID. For Tekton systems, you need the specific PipelineRun name to target and re-trigger the failed execution.