OpenParable
Skip to content
← Back to skills

GH Debug

DevOps & Security
gh-debug

GH Debug is an Agent Skill for devops & security published in the FastLED/FastLED repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Debug GitHub Actions build failures by fetching and analyzing workflow logs. Use when CI/CD pipelines fail and you need to identify the root cause.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/FastLED/FastLED/blob/HEAD/.claude/skills/gh-debug/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gh-debug, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Pull GitHub Actions logs for a workflow run, parse them to identify errors, and provide a clear diagnostic report.

Arguments: $ARGUMENTS

Primary Method (Recommended): Use the Python script for efficient log analysis:

uv run ci/tools/gh_debug.py $ARGUMENTS

This script:

  • Tries build-summary artifacts first (small, focused files uploaded by CI — much faster)
  • Falls back to streaming full logs if no summary artifact is available
  • Filters for errors in real-time
  • Stops after finding 10 errors (configurable with --max-errors)
  • Shows context around each error (5 lines before/after, configurable with --context)

Fallback Method: If the Python script fails, use manual analysis:

Smart Log Fetching Strategy

  1. Identify failed jobs/steps using gh run view <run-id> --log-failed
  2. For each failed step, use targeted log extraction with grep filters
  3. Parse logs for: compilation errors, test failures, runtime issues
  4. Extract error context: ~10 lines before and after each error

Input Handling

Handle:

  • Run IDs (e.g., "18391541037")
  • Workflow URLs
  • Most recent failed run if no argument provided (use gh run list --status failure --limit 1)

Output Format

Provide:

  • Workflow name and run number
  • Job(s) that failed with step names
  • Specific error messages with surrounding context (max ~50 lines per error)
  • File paths and line numbers where applicable
  • Suggested next steps or potential fixes