actions-debugging

A troubleshooting guide for failed GitHub Actions workflows. GitHub Actions is GitHub’s system for automatically running tasks such as tests, builds, and deployments when code changes.

In plain words
What is it for?
Use it to investigate broken continuous-integration pipelines, deployment failures, flaky tests, runtime changes, and regressions in GitHub Actions.
Why use it?
It helps locate the root cause by examining workflow runs, failed job logs, flaky tests, and differences between successful and failed runs.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/drvoss/everything-copilot-cli/actions-debugging
Any agent
npx skills add drvoss/everything-copilot-cli --skill actions-debugging
Clone the repo
git clone --depth 1 https://github.com/drvoss/everything-copilot-cli

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,093 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.01093
Opus 5 $0.00014 $0.00547
Sonnet 5 $0.00006 $0.00219
Haiku 4.5 $0.00003 $0.00109

Measured yesterday against content hash a946c09c3906, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

actions-debugging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/copilot-native-workflows/skills/actions-debugging/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Actions Debugging

Why This is Copilot-Exclusive

Copilot CLI provides structured access to GitHub Actions through its built-in MCP server. You can list workflows, inspect run details, download job logs, and analyze failures — all via typed tool calls that return structured data. Claude Code has no GitHub Actions integration whatsoever; debugging CI requires manually navigating the GitHub web UI or parsing raw gh run view output.

When to Use

  • A CI pipeline fails and you need to understand why — fast
  • Investigating flaky tests across multiple workflow runs
  • Auditing workflow run times and usage patterns
  • Debugging deployment pipeline failures in staging/production
  • Comparing successful vs failed runs to find regressions

Workflow

1. List Workflows in a Repository

Tool: github-mcp-server-actions_list
  method: "list_workflows"
  owner: "my-org"
  repo: "my-app"

2. List Recent Runs for a Workflow

Tool: github-mcp-server-actions_list
  method: "list_workflow_runs"
  owner: "my-org"
  repo: "my-app"
  resource_id: "ci.yml"
  workflow_runs_filter: { "status": "completed", "branch": "main" }

3. Get Failed Job Logs

This is the killer feature — pull logs directly for analysis:

Tool: github-mcp-server-get_job_logs
  owner: "my-org"
  repo: "my-app"
  run_id: 12345678
  failed_only: true
  return_content: true
  tail_lines: 200

4. Inspect a Specific Job

Tool: github-mcp-server-actions_get
  method: "get_workflow_job"
  owner: "my-org"
  repo: "my-app"
  resource_id: "98765432"

5. Check Run Usage and Timing

Tool: github-mcp-server-actions_get
  method: "get_workflow_run_usage"
  owner: "my-org"
  repo: "my-app"
  resource_id: "12345678"

Examples

"Why Did My CI Fail?"

"My latest push to feature/auth-refactor failed CI. Show me what went wrong."

Copilot workflow:

  1. list_workflow_runs filtered by branch feature/auth-refactor
  2. Takes the most recent failed run
  3. list_workflow_jobs to find which job(s) failed
  4. get_job_logs with failed_only: true to pull the error output
  5. Analyzes the logs, identifies the root cause, suggests a fix

Read the full file on GitHub · 148 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 148 lines · 28 tokens per session scan A a946c09c3906

Subscribe to this mod's changes

actions-debugging is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 1,093 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

winui-design

Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…

microsoft/win-dev-skills · 119 tokens

winui-dev-workflow

Build and run workflow for WinUI 3 apps with WinApp CLI 0.6+ — project creation with winapp new, project-mode winapp run, BuildAndRun.ps1 analyzer integration, crash diagnosis, and prerequisites. Use when creating, building, running, or fixing build errors in a WinUI 3 project.

microsoft/win-dev-skills · 73 tokens

winui-packaging

MSIX packaging, code signing, and distribution for WinUI 3 apps — build for release, certificate generation (winapp cert generate), certificate trust, code signing (winapp sign), self-contained deployment, CI/CD with GitHub Actions, and Microsoft Store submission. Use when preparing for release, creating MSIX…

microsoft/win-dev-skills · 86 tokens

winui-session-report

Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.

microsoft/win-dev-skills · 61 tokens

microsoft-build

Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…

microsoft/Build-CLI · 109 tokens

journey-template

Create new agentic journeys from app ideas. Generates README.md (learner walkthrough), PLAN.md (AI-readable spec), and app-specific skills for OSS deployments. Supports any stack (Node.js, Python, .NET, Java, Swift, Kotlin) and Azure service (Container Apps, AKS, Functions, App Service). USE FOR: new journey, scaffold…

DanWahlin/github-azure-agentic-journeys · 153 tokens