SKILL.md
GitHub Actions Management via MCP
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 |
getrunlogs |
Get the logs URL for a run (zip download) |
rerun_workflow |
Re-run an entire workflow run |
rerunfailedjobs |
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:
getrunfor details, then decide whether torerunfailed_jobsor investigate logs triggerworkflowrequires the workflow file name and a branch — the workflow must have aworkflowdispatchtrigger
Key Patterns
- All tools require
ownerandrepoparameters (e.g.,owner: "ofershap",repo: "my-project") listrunssupportsstatusfilter: "completed", "inprogress", "queued", "failure", "success"rerunfailedjobsis preferred overrerun_workflow; it is faster and cheapertriggerworkflowneedsworkflowid(filename like "ci.yml") andref(branch name)
Error Scenarios
- 401/403 from GitHub:
GITHUB_TOKENmissing, expired, or lacks Actions scope on the repo - Run or workflow not found: double-check
owner,repo, and numeric run id fromlist_runs triggerworkflowrejected: workflow file lacksworkflowdispatchor branchrefis wronggetrunlogsreturns a zip URL only: download and unzip outside the tool to read full log text
Safety
- Prefer
rerunfailedjobsover 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