agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/cancel-pipeline/SKILL.md

cancel-pipeline

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Cancel a running or stuck Tekton pipeline. Use when pipeline is stuck, wrong build started, need to free cluster resources, or want to retry with different parameters.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    If run_name not specified and only one running: use it

    line 35
  2. Distinctive:

    If multiple: ask user to specify

    line 36
  3. Distinctive:

    Verify status is "running" before cancel

    line 41

≈ “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

Cancel Pipeline

Cancel running or stuck Tekton (Konflux) pipelines. Also supports GitLab CI cancellation.

Inputs

InputTypeDefaultPurpose
run_namestring-PipelineRun name (lists running if not specified)
namespacestringaap-aa-tenantKonflux/Tekton namespace
deleteboolfalseDelete PipelineRun after cancelling
list_onlyboolfalseJust list running pipelines
pipeline_idint-GitLab CI pipeline ID (for GitLab)
projectstringautomation-analytics/automation-analytics-backendGitLab project

Workflow

1. Load Persona

  • persona_load("release") — for Tekton tools

2. GitLab Path (if pipeline_id)

  • gitlab_ci_cancel(project="{{ project }}", pipeline_id="{{ pipeline_id }}")

3. Tekton Path

  • tkn_pipelinerun_list(namespace="{{ namespace }}", limit=20)
  • Parse for running pipelines
  • If run_name not specified and only one running: use it
  • If multiple: ask user to specify

4. Get Details (if not list_only)

  • tkn_pipelinerun_describe(run_name="{{ target_run }}", namespace="{{ namespace }}")
  • Verify status is "running" before cancel

5. Cancel

  • tkn_pipelinerun_cancel(run_name="{{ target_run }}", namespace="{{ namespace }}")

6. Delete (if delete=true)

  • tkn_pipelinerun_delete(run_name="{{ target_run }}", namespace="{{ namespace }}")

7. Error Recovery

  • "no route to host" → vpn_connect(), kube_login("konflux")
  • "unauthorized" → kube_login("konflux")
  • "pipelinerun not found" → already completed; list with tkn_pipelinerun_list()

8. Memory

  • memory_session_log("Cancelled pipeline", "{{ run_name }}, namespace={{ namespace }}")

Output

Report: running pipelines list, target run, cancel status, delete status (if applicable), and retry commands (tkn_pipeline_start).

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