gh-ci-remote-debug

Diagnose CI/CD failures by triggering and monitoring GitHub Actions workflows with gh CLI.

3|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ZHLX2005/sl --skill gh-ci-remote-debug-zhlx2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-ci-remote-debug
Source: https://github.com/ZHLX2005/sl/tree/main/skills/gh-ci-remote-debug
Command: npx skills add https://github.com/ZHLX2005/sl --skill gh-ci-remote-debug-zhlx2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When CI/CD deployments fail or containers crash on startup but cannot be reproduced locally, this Skill helps you reproduce and diagnose the issue directly in the GitHub Actions environment using the gh CLI. ## Core Features & Use Cases - Debug Workflow Creation: Generates a workflow_dispatch-triggered GitHub Actions workflow that mirrors your build and Docker Compose startup steps, with mandatory timeouts to avoid resource waste. - Remote Triggering and Monitoring: Triggers workflows with gh workflow run and tracks run status, enforcing verification with gh run view before reading logs. - Failure Log Retrieval: Fetches failed or complete job logs via gh run view --job=<job_id> --log-failed for root-cause analysis. - Use Case: Your Docker container crashes only in CI. Create a debug workflow, trigger it remotely, monitor the run, verify its final state, and pull the last 100 lines of container logs to find the crash cause. ## Quick Start Create a debug workflow for my failing deployment, trigger it with gh CLI, monitor the run, and show me the failure logs.

Frequently Asked Questions about gh-ci-remote-debug

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

FAQPage Schema
How do I debug a GitHub Actions workflow failure remotely?

Create a workflow_dispatch-triggered debug workflow that reproduces your build and Docker Compose steps, then trigger it with gh workflow run. Monitor the run and verify its final state with gh run view before reading logs.

How to get failed job logs from GitHub Actions using gh CLI?

Run gh run view --job=<job_id> --log-failed to fetch only the failed step logs, or use --log for the complete job output. Always confirm the run has finished with gh run view <run_id> first.

Why does my GitHub Actions log show stale or missing data after monitoring?

A monitor reporting completion does not guarantee the workflow finished. Always verify the actual run state with gh run view <run_id>; if it is still in_progress, keep waiting before reading logs.

Can I debug a Docker container that crashes only in CI?

Yes. Add docker compose build and docker compose up --abort-on-container-exit steps to a debug workflow, set a timeout-minutes limit, and capture logs with docker compose logs --tail=100 on failure.

Why should timeout-minutes be set on Docker Compose steps in CI?

Without a timeout, a hung container can consume runner minutes indefinitely. Setting timeout-minutes (for example 8) ensures the step terminates and the failure log step still executes.