ci-health-check

Monitor GitHub Actions workflow runs and diagnose failures.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill ci-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-health-check
Source: https://github.com/tnez/docent/tree/main/skills/devops/ci-health-check
Command: npx skills add https://github.com/tnez/docent --skill ci-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh cli, git cli, npm.

What problem does it solve?

CI/CD pipelines can fail for various reasons, leading to delays and frustration. This Skill automates the process of checking workflow statuses, troubleshooting failures, and analyzing logs, quickly pinpointing issues so you can resolve them efficiently.

Core Features & Use Cases

  • Workflow Status Overview: Get a quick summary of recent GitHub Actions runs.
  • Detailed Failure Analysis: Drill down into failed jobs and view logs to diagnose root causes.
  • Re-run & Validate: Easily re-run failed workflows and validate fixes, ensuring your pipelines are always green.
  • Use Case: Your CI pipeline just failed on a critical branch. Instead of manually navigating GitHub, use this Skill to instantly identify the failing job, view its logs, and re-run it after applying a fix, all from your agent.

Quick Start

Check the health of the CI/CD pipelines in this project.

Frequently Asked Questions about ci-health-check

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

FAQPage Schema
How do I check GitHub Actions workflow status and diagnose CI/CD failures?

Monitor GitHub Actions workflow runs using gh CLI to retrieve status, identify failed jobs, inspect logs, and pinpoint root causes without manual GitHub navigation. This automates status checks and failure diagnosis across repositories.

Can I automate troubleshooting of failed CI/CD pipelines with GitHub Actions?

Yes. Automate CI/CD health checks by listing recent runs, analyzing failed-job logs, and re-running workflows after fixes. The Skill uses gh CLI and git to diagnose and remediate failures end-to-end.

What do I need to run CI/CD health checks on my GitHub repositories?

You need gh CLI, git CLI, npm, and repository read access (write access for re-running workflows). The Skill executes commands to list runs, view logs, and trigger re-runs across GitHub Actions workflows.

How do I quickly identify which job failed in my GitHub Actions workflow?

Drill down into failed runs by viewing detailed job logs and error output. The Skill retrieves and displays failure context so you can identify the root cause without navigating GitHub manually.

Can I re-run failed workflows and validate fixes automatically?

Yes. After diagnosing a failure, re-run the workflow and confirm it passes, keeping your CI pipeline green. The Skill automates re-run and validation steps using gh CLI commands.

What types of CI/CD issues can this Skill help me troubleshoot?

Troubleshoot GitHub Actions workflow failures by analyzing job logs, viewing error messages, and identifying blockers. Works across repositories and covers status retrieval, failed-job analysis, and re-run remediation scenarios.