agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/ci-retry/SKILL.md

ci-retry

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Retry a failed CI pipeline. Works with GitLab CI and Konflux/Tekton. Use when user says "retry pipeline", "retry CI", "rerun pipeline", or "retry MR !1234".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If mr_id → GitLab (get pipeline from MR)

    line 27
  2. Very specific:

    If mr_id: gitlab_ci_status(project="{{ project }}", mr_id="{{ mr_id }}") — extract pipeline_id

    line 32
  3. Very specific:

    If wait: poll gitlab_ci_status until complete

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CI Retry

Retry failed GitLab CI or Konflux/Tekton pipelines.

Inputs

InputTypeDefaultPurpose
mr_idint-GitLab MR ID — retries its pipeline
pipeline_idint-GitLab CI pipeline ID
tekton_runstring-Tekton PipelineRun name
projectstringautomation-analytics/automation-analytics-backendGitLab project
namespacestringaap-aa-tenantKonflux/Tekton namespace
waitboolfalseWait for pipeline to complete (up to 15 min)

Workflow

1. Determine CI System

  • If tekton_run → Tekton
  • If pipeline_id → GitLab
  • If mr_id → GitLab (get pipeline from MR)

2. GitLab Path

  • persona_load("developer")
  • If mr_id: gitlab_ci_status(project="{{ project }}", mr_id="{{ mr_id }}") — extract pipeline_id
  • gitlab_ci_status(project="{{ project }}", pipeline_id="{{ pipeline_id }}") — get failed jobs
  • gitlab_ci_retry(project="{{ project }}", job_id="{{ failed_job_id }}")
  • If wait: poll gitlab_ci_status until complete

3. Tekton Path

  • persona_load("release")
  • tkn_pipelinerun_describe(run_name="{{ tekton_run }}", namespace="{{ namespace }}")
  • tkn_pipelinerun_logs(run_name="{{ tekton_run }}", namespace="{{ namespace }}", all_tasks=true) — if failed
  • Re-trigger: tkn_pipeline_start or equivalent (depends on tool availability)

4. Error Recovery

  • GitLab "no such host" → vpn_connect()
  • GitLab "unauthorized" → check GitLab token
  • Tekton "unauthorized" → kube_login("konflux")
  • Tekton "pipelinerun not found" → list with tkn_pipelinerun_list() for correct name

5. Memory

  • memory_session_log("Retried CI pipeline", "target={{ target }}, project={{ project }}")

Output

Report: system (gitlab/tekton), target, status, retry status, and monitor commands.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free