smithery.ai

github-actions-failure-debugging

Guide for debugging failing GitHub Actions workflows. Use this when asked to debug failing GitHub Actions workflows.

First seen Mar 31, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 942 B
  • docs SUMMARY.md 156 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

To debug failing GitHub Actions workflows in a pull request, follow this process, using tools provided from the GitHub MCP Server:

  1. Use the listworkflowruns tool to look up recent workflow runs for the pull request and their status
  2. Use the summarizejoblog_failures tool to get an AI summary of the logs for failed jobs, to understand what went wrong without filling your context windows with thousands of lines of logs
  3. If you still need more information, use the getjoblogs or getworkflowrun_logs tool to get the full, detailed failure logs
  4. Try to reproduce the failure yourself in your own environment.
  5. Fix the failing build. If you were able to reproduce the failure yourself, make sure it is fixed before committing your changes.