Agent skill · software engineering · sickn33
github-actions-debugger
Specialized skill for diagnosing, analyzing, and fixing failing GitHub Actions workflows by parsing run logs and pipeline definitions.
Why this skill is useful
Provides domain-specific knowledge for diagnosing and fixing GitHub Actions workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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.APIKEY }}). 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). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/github-actions-debugger--a38a8d