github-actions-failure-debugging

Étoiles170

Forks86

Mis à jour24 mars 2026 à 16:12

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

LanceMcCarthy

LanceMcCarthy/DevOpsExamples

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

winui-app

LanceMcCarthy/DevOpsExamples

Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.

2026-04-08170

configure-telerik-nuget

LanceMcCarthy/DevOpsExamples

Helps setup, configure and manage Telerik NuGet feeds in your repo's nuget.config file.

2026-03-24170

name	github-actions-failure-debugging
description	Guide for debugging failing GitHub Actions workflows. Use this when asked to debug failing GitHub Actions workflows.
version	1.0.0
author	Lance McCarthy
homepage	https://github.com/DevOpsExamples/.github
source	https://github.com/DevOpsExamples/.github/tree/main/skills/github-actions-failure-debugging

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

Use the list_workflow_runs tool to look up recent workflow runs for the pull request and their status
Use the summarize_job_log_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
If you still need more information, use the get_job_logs or get_workflow_run_logs tool to get the full, detailed failure logs
Try to reproduce the failure yourself in your own environment.
Fix the failing build. If you were able to reproduce the failure yourself, make sure it is fixed before committing your changes.ng to use environment variable expansion instead of hardcoded API key values.

Added version field to frontmatter.