Menu

Individual skill

actions-debugging

Use when a GitHub Actions workflow fails — diagnose the run log, identify the root cause, and apply a targeted fix

skills/copilot-exclusive/actions-debugging/SKILL.md

Read pinned source

Source commit 76ee15b3b90d544cfffa70421a8788fda0f4ebba

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
48
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GitHub Actions Debugging

## Why This is Copilot-Exclusive

GitHub access is built into Copilot CLI with no extra setup: the built-in GitHub MCP server (full
tool set when `gh` is absent, or when restored with the flags in the note below) or `gh`, which
the model is expected to use when it is installed. Either way you can list workflows, inspect run details, download job logs,
and analyze failures in one conversation.
What is exclusive is the built-in GitHub MCP server, which needs no token or extension setup; when `gh` is installed, the model mostly uses `gh`, which any agent with a shell can also run.

> **Note:** When `gh` is on PATH, Copilot CLI omits the Actions MCP tools (`actions_list`, `actions_get`, `get_job_logs`) and the model is expected to use `gh` instead,
> e.g. `gh run list --workflow <file>`, `gh run view <run-id> --log-failed`, `gh run view --job <job-id> --log`. To call the MCP tools,
> start the session with `--add-github-mcp-tool=<name>` for every GitHub MCP tool you need (it replaces the default set, so include default ones you still use), or `--enable-all-github-mcp-tools`, which also enables write tools.