Agent skill

GitHub Actions Debugger

by sickn33 in sickn33/agentic-awesome-skills

Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.

MITAuto-check passedDevOps & Cloud

Install GitHub Actions Debugger

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill github-actions-debugger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills github-actions-debugger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-actions-debugger .claude/skills/github-actions-debugger && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-actions-debugger
GitHub stars
47k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
610 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.

  • Works in 4 steps: Log Ingestion & Redaction: Analyze the… → Context Mapping: Cross-reference the… → Root Cause Analysis: Identify if the… → …
  • Tasks that involve CI/CD
  • SKILL.md covers Overview, When to Use, How It Works and Best Practices, plus 5 more sections
  • Needs API_KEY and DEPLOY_API_KEY

What it does

GitHub Actions Debugger is an agent skill from sickn33/agentic-awesome-skills. Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve CI/CD

Example prompts

  • “/github-actions-debugger”

Requirements

  • Python 3
  • Node.js
  • A credential in API_KEY
  • A credential in DEPLOY_API_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Log Ingestion & Redaction: Analyze the provided GitHub Actions workflow log (often exported as a raw text file or pasted directly)…
  2. Context Mapping: Cross-reference the failure point with the specific step and job in the .github/workflows/*.yml definition.
  3. Root Cause Analysis: Identify if the failure is due to
  4. Resolution Proposal: Provide a direct diff of the .yml file or the underlying script that needs to be modified.

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are diff).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY
    • DEPLOY_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Actions Debugger loads about 1.4k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 610 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 610 words, ~1,381 tokens.

Download SKILL.mdSave it as .claude/skills/github-actions-debugger/SKILL.md (or your agent's skills folder).
name
github-actions-debugger
description
Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.
category
devops
risk
safe
source
community
source_type
community
date_added
2026-06-25
author
Owais
tags
github-actions, ci-cd, devops, debugging, workflows
tools
claude, cursor, gemini, antigravity

GitHub Actions Pipeline Debugger

Overview

This skill is designed to act as an expert CI/CD diagnostician. It focuses specifically on reading raw logs from failed GitHub Actions, identifying the root cause of the crash or failure, and outputting the precise YAML or code changes required to fix the pipeline.

When to Use

  • Use when a GitHub Actions workflow fails unexpectedly and the error log is long, obscure, or misleading.
  • Use when debugging dependency mismatch errors, missing secrets, caching issues, or runner environment problems in CI.
  • Use to optimize slow pipelines by identifying bottlenecks in workflow steps.
  • Use to update and modernize deprecated actions or workflow syntax.

How It Works

  1. Log Ingestion & Redaction: Analyze the provided GitHub Actions workflow log (often exported as a raw text file or pasted directly). CRITICAL SAFETY REQUIREMENT: The user/agent must redact all sensitive credentials, secrets, tokens, private keys, and internal system paths from the logs before pasting or uploading them.
  2. Context Mapping: Cross-reference the failure point with the specific step and job in the .github/workflows/*.yml definition.
  3. Root Cause Analysis: Identify if the failure is due to:
    • Missing or misconfigured secrets (${{ secrets.API_KEY }}).
    • Node/Python/OS environment version mismatches.
    • Flaky tests or timeout limits.
    • Syntax errors in bash scripts run within the run: block.
    • Invalid action versions or deprecated actions.
  4. Resolution Proposal: Provide a direct diff of the .yml file or the underlying script that needs to be modified.

Best Practices

  • Provide Full Context: Always review both the workflow definition (.yml file) and the failure log simultaneously to ensure accurate diagnosis.
  • Check Action Versions: Many failures are caused by deprecated runtime versions (e.g., Node.js 16) in older third-party actions (e.g., actions/checkout@v2). Always recommend upgrading to the latest major versions (e.g., v4).
  • Permissions Audit: Ensure the workflow has the correct permissions: block if it's attempting to write to the repository, packages, or deploy environments.
  • Reproducibility: If a test fails in CI but passes locally, investigate environment differences such as timezone, headless browser state, memory limits, or parallel execution race conditions.

Examples

Example 1: Fixing a Deprecated Node.js Action Version Error

Failing Log:

text
Warning: The Go/Node.js/Python version used by this action is deprecated.
Error: Node.js 16 actions are deprecated. Please update to use Node.js 20.

Proposed Fix Diff:

diff
       - name: Checkout Code
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
Example 2: Diagnosing and Fixing a Missing Repository Secret

Failing Log:

text
Run npm run deploy
  npm run deploy
  shell: /usr/bin/bash -e {0}
Error: API Key is required for deployment. Process exited with code 1.

Proposed Fix Diff:

diff
       - name: Deploy App
         run: npm run deploy
+        env:
+          DEPLOY_API_KEY: ${{ secrets.DEPLOY_API_KEY }}
Show full SKILL.md (247 more words)Show less

Security & Safety Notes

  • Credential Exposure & Raw Log Redaction: Under no circumstances should raw logs containing unmasked secrets, private URLs, deployment targets, or tokens be processed without prior redaction. Always ensure the user or agent redacts all sensitive info before ingestion.
  • Dry-Run Mode: When recommending modifications to bash script steps inside workflows, ensure you suggest adding flags like --dry-run or staging execution where possible to prevent unintended side effects in downstream environments during debugging.

Limitations

  • The skill cannot securely read repository secrets. It can only infer missing or malformed secrets if the log complains about undefined environment variables or authentication failures.
  • It cannot execute the GitHub action itself to test the fix; validation requires pushing the proposed fix to the repository and triggering a workflow run.
  • Network-related transient failures (e.g., a package registry being down temporarily) might be incorrectly diagnosed as structural workflow issues if not carefully analyzed.

Common Pitfalls

  • Ignoring Transient Failures: Mistaking temporary network dropouts or registry downtime (e.g., npm or pip install errors) for actual code or configuration bugs. Always check if a rerun succeeds before attempting heavy changes.
  • Hardcoding Tokens: Fixing authentication errors by hardcoding secrets or API tokens directly into the YAML files instead of utilizing GitHub Secrets (${{ secrets.SECRET_NAME }}).
  • Overlooking Caching Side Effects: Forgetting that outdated cache keys can keep corrupt dependencies loaded. If dependency installation is failing, try running a job with actions caching bypassed.
  • @devops-troubleshooter - General DevOps and infrastructure issue resolution.
  • @cicd-automation-workflow-automate - For creating new CI/CD pipelines from scratch.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/github-actions-debugger of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

GitHub Actions Debugger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Actions Debugger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Actions Debugger this skillsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
GitHub Actions Templatesbartstc/vite-ts-react-template12213 repos~1.9kAutomated safety check: PassMIT
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Repo Hygiene Scan and FixQwenLM/qwen-code28k—~1.7kAutomated safety check: PassApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2596 repos~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 13 repos~1.9k tokens
    DevOps & CloudAuto-check passed
  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.

    28k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    259 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about GitHub Actions Debugger

What does GitHub Actions Debugger do?

Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions. GitHub Actions Debugger is an agent skill from sickn33/agentic-awesome-skills. Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.

When should I use GitHub Actions Debugger?

GitHub Actions Debugger fits situations like: tasks that involve CI/CD.

How do I install GitHub Actions Debugger in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-actions-debugger -a claude-code`. Or copy the skill folder (skills/github-actions-debugger in sickn33/agentic-awesome-skills) into .claude/skills/github-actions-debugger in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Actions Debugger in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-actions-debugger -a codex`. Or copy the skill folder (skills/github-actions-debugger in sickn33/agentic-awesome-skills) into .agents/skills/github-actions-debugger in your project. Codex loads it when a task matches its description.

Can I use GitHub Actions Debugger in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill github-actions-debugger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-actions-debugger, .gemini/skills/github-actions-debugger, .github/skills/github-actions-debugger and .opencode/skills/github-actions-debugger in your project.

What does GitHub Actions Debugger need to run?

Going by SKILL.md and its folder, GitHub Actions Debugger needs credentials named API_KEY and DEPLOY_API_KEY. Our summary lists: Python 3; Node.js; A credential in API_KEY; A credential in DEPLOY_API_KEY.

Does GitHub Actions Debugger access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is GitHub Actions Debugger safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Actions Debugger use?

GitHub Actions Debugger is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Actions Debugger use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Actions Debugger?

Skills that share tags, products or a category with GitHub Actions Debugger: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Actions Debugger?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.