debugging-workflows

Diagnose GitHub Agentic Workflow issues by analyzing logs and auditing runs.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill debugging-workflows-kaushal-waygood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-workflows
Source: https://github.com/kaushal-waygood/agentic-self-healing-ci/tree/main/.github/skills/debugging-workflows
Command: npx skills add https://github.com/kaushal-waygood/agentic-self-healing-ci --skill debugging-workflows-kaushal-waygood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging GitHub Agentic Workflows can be time-consuming without clear visibility into logs and run audits. This skill provides structured guidance to analyze workflow logs, audit specific runs, and troubleshoot failures across agentic processes.

Core Features & Use Cases

  • Log retrieval and analysis: Download, parse, and summarize logs from recent workflow runs to identify failures and bottlenecks.
  • Run auditing and issue diagnosis: Inspect individual runs, extract error signals, and correlate events to root causes.
  • Operational guidance: Step-by-step debugging procedures, guardrails, and safe prompts to fix issues without exposing sensitive data.

Quick Start

Download the latest Agentic Workflow logs and generate a concise diagnostic summary of any anomalies.

Frequently Asked Questions about debugging-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug GitHub Actions agentic workflow failures?

To debug GitHub Actions agentic workflow failures, download and parse logs from recent runs to identify anomalies, audit specific runs to extract error signals, and follow guided troubleshooting steps to resolve issues.

What is the best way to analyze GitHub Actions logs for bottlenecks?

Analyzing GitHub Actions logs involves retrieving run data, parsing output to summarize events, and correlating those events to pinpoint root causes and bottlenecks within the agentic workflow.

Can I use this to troubleshoot production-grade agentic workflows?

Yes, you can troubleshoot production-grade agentic workflows by inspecting individual runs, extracting error signals, and applying safe prompts and guardrails to fix issues without exposing sensitive data.

How do I audit a specific GitHub Actions run to find the root cause?

Auditing a specific GitHub Actions run requires inspecting the run to extract error signals, correlating events to diagnose the root cause, and generating a concise diagnostic summary of anomalies.

Does debugging GitHub Agentic Workflows require the GitHub CLI?

Debugging GitHub Agentic Workflows executes reproducible steps via the CLI and GitHub CLI, requiring access to download logs and audit runs for effective troubleshooting and issue resolution.