debug-workflow

Diagnose GitHub Actions workflow failures using gh run logs and local reproduction commands.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill debug-workflow-nsuberi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-workflow
Source: https://github.com/nsuberi/proto-portal-showcase-hub/tree/main/.claude/skills/debug-workflow
Command: npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill debug-workflow-nsuberi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a systematic, reproducible process to diagnose and remediate GitHub Actions workflow failures across a multi-project monorepo, reducing time-to-recovery for broken pipelines and stalled deployments.

Core Features & Use Cases

  • Log-first diagnosis: Use GitHub CLI to locate failed runs, extract failed job and step logs, and download full artifacts for inspection.
  • Categorized troubleshooting: Targeted guidance for authentication/permissions, Terraform state locks and plan/apply errors, build/install and package manager failures, unit and integration test failures, Docker/container issues, lint breaks, and deployment problems.
  • Reproduction & remediation: Commands and strategies to reproduce failures locally (yarn, terraform, docker-compose), run forced Terraform unlocks or workflow reruns, verify secrets/variables, and confirm CloudFront/S3 deployment outputs.
  • Use case example: When Playwright integration tests fail after deploy, the Skill helps confirm CloudFront propagation, validate Terraform outputs for API Gateway URLs, and ensure the Playwright browser was installed correctly.

Quick Start

Use the debug-workflow skill to diagnose a failed GitHub Actions run by providing the run ID or the workflow failure logs.

Frequently Asked Questions about debug-workflow

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

FAQPage Schema
Why does my Playwright integration test fail after deploy in GitHub Actions?

Resolve Terraform state lock errors in GitHub Actions by accessing the run logs via gh CLI to identify the lock, then executing a terraform-force-unlock workflow or command to release the stuck state.

How do I troubleshoot Docker and Terraform step errors in a monorepo CI/CD pipeline?

Playwright integration test failures after deploy often stem from incomplete CloudFront propagation, invalid Terraform outputs for API Gateway URLs, or incorrect Playwright browser installation, which can be verified using downloaded CI logs.

Do I need GitHub CLI access to debug a failed CI/CD workflow?

Troubleshoot Docker and Terraform step errors in a monorepo by downloading the failed GitHub Actions artifacts, verifying repository secrets and variables, and running local docker-compose and terraform reproduction commands.

How do I fix GitHub Actions deployment problems with CloudFront and S3 outputs?

You need GitHub CLI access to debug a failed CI/CD workflow because it is required to locate failed runs, extract failed job and step logs, and download full artifacts for inspection.

How do I fix GitHub Actions deployment problems with CloudFront and S3 outputs?

Fix GitHub Actions deployment problems with CloudFront and S3 outputs by inspecting the deployment logs, verifying Terraform outputs for API Gateway URLs, and confirming CloudFront propagation and S3 deployment artifacts.