How do I install the Github Actions Debugging skill?

Run npx get-skill add tomevault-io/github-actions-debugging in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Github Actions Debugging skill do?

Debug and fix GitHub Actions CI/CD failures Use when this capability is needed. It is listed under DevOps & Infra on SkillMD.

Is Github Actions Debugging safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Actions Debugging?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Actions Debugging free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Actions Debugging?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Actions Debugging by tomevault-io

Name: Github Actions Debugging
Author: tomevault-io

File contents

GitHub Actions Debugging Skill

Overview

Diagnose and fix GitHub Actions workflow failures with systematic checks.

Usage

/github-actions-debugging

Identity

Role: DevOps Engineer Objective: Analyze failed workflow runs and implement fixes to get the build Green.

Diagnostic Playbook

Step 1: Log Retrieval

Action: If run locally, replicate the failure. If remote, read the gh run view logs. Keywords to Search:

Process completed with exit code 1
npm ERR!
Module not found
Permission denied

Step 2: Context Analysis

Env: Is the Runner Ubuntu-latest? Node version mismatch?
Secrets: Are secrets missing? (Logs show *** or empty values).
Paths: Is the working directory correct? (working-directory: ./frontend).

Step 3: Local Reproduction

Do not code blindly. Try to run the exact command locally.

If npm test failed in CI -> Run npm test locally.
If it works locally but fails in CI -> Check Node Versions or Missing Artifacts (unaccounted generated files).

Common Fixes

1. Dependency Caching

Issue: Build slow or failing on install. Fix:

- uses: actions/setup-node@v3
  with:
    cache: 'npm'

2. Flaky Tests

Issue: Test fails randomly. Fix: Mark as flaky, improve wait logic, or increase timeout.

3. Missing Perms

Issue: 403 on Push/Release. Fix: permissions: write-all or specific scopes in YAML.

Workflow

Command: /debug-action <run-id>

Read logs.
Hypothesize root cause.
Propose YAML fix or Code fix.
Commit with message ci: fix workflow failure.

Outputs

CI/CD failure analysis and remediation summary.

Related Skills

/deploy - Deployment workflow checks

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: github-actions-debuggingdescription: Debug and fix GitHub Actions CI/CD failures Use when this capability is needed.---# GitHub Actions Debugging Skill## OverviewDiagnose and fix GitHub Actions workflow failures with systematic checks.## Usage```/github-actions-debugging```## Identity**Role**: DevOps Engineer**Objective**: Analyze failed workflow runs and implement fixes to get the build Green.## Diagnostic Playbook### Step 1: Log Retrieval**Action**: If run locally, replicate the failure. If remote, read the `gh run view` logs.**Keywords to Search**:- `Process completed with exit code 1`- `npm ERR!`- `Module not found`- `Permission denied`### Step 2: Context Analysis- **Env**: Is the Runner Ubuntu-latest? Node version mismatch?- **Secrets**: Are secrets missing? (Logs show `***` or empty values).- **Paths**: Is the working directory correct? (`working-directory: ./frontend`).### Step 3: Local ReproductionDo not code blindly. Try to run the exact command locally.- If `npm test` failed in CI -> Run `npm test` locally.- If it works locally but fails in CI -> Check **Node Versions** or **Missing Artifacts** (unaccounted generated files).## Common Fixes### 1. Dependency Caching**Issue**: Build slow or failing on install.**Fix**:```yaml- uses: actions/setup-node@v3 with: cache: 'npm'```### 2. Flaky Tests**Issue**: Test fails randomly.**Fix**: Mark as flaky, improve wait logic, or increase timeout.### 3. Missing Perms**Issue**: `403` on Push/Release.**Fix**: `permissions: write-all` or specific scopes in YAML.## Workflow**Command**: `/debug-action <run-id>`1. Read logs.2. Hypothesize root cause.3. Propose YAML fix or Code fix.4. Commit with message `ci: fix workflow failure`.## Outputs- CI/CD failure analysis and remediation summary.## Related Skills- `/deploy` - Deployment workflow checks---> Converted and distributed by [TomeVault](https://tomevault.io/claim/etroxtaran) — claim your Tome and manage your conversions.

Frequently asked questions

Github Actions Debugging