Use this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments.
Available Tools
| Tool | What it does |
|---|---|
list_workflows |
List all workflow files in a repository |
list_runs |
List workflow runs (filter by workflow or status) |
get_run |
Get details of a specific workflow run |
get_run_logs |
Get the logs URL for a run (zip download) |
rerun_workflow |
Re-run an entire workflow run |
rerun_failed_jobs |
Re-run only the failed jobs from a run |
cancel_run |
Cancel an in-progress or queued run |
list_artifacts |
List artifacts produced by a workflow run |
trigger_workflow |
Trigger a workflow via workflow_dispatch |
Workflow
- Use
list_runswithownerandrepoto see recent runs and their status - For failed runs:
get_runfor details, then decide whether torerun_failed_jobsor investigate logs trigger_workflowrequires the workflow file name and a branch — the workflow must have aworkflow_dispatchtrigger
Key Patterns
- All tools require
ownerandrepoparameters (e.g.,owner: "ofershap",repo: "my-project") list_runssupportsstatusfilter: "completed", "in_progress", "queued", "failure", "success"rerun_failed_jobsis preferred overrerun_workflow— it's faster and cheapertrigger_workflowneedsworkflow_id(filename like "ci.yml") andref(branch name)
Safety
- Prefer
rerun_failed_jobsover fullrerun_workflowto avoid unnecessary compute - Confirm before
cancel_run— the user may want the run to finish trigger_workflowcan trigger deployments — always confirm the target branch