investigate-ci

Diagnose GitHub Actions workflow failures and suggest remediation steps.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/mostafa-drz/claude-skills --skill investigate-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-ci
Source: https://github.com/mostafa-drz/claude-skills/tree/main/code/investigate-ci
Command: npx skills add https://github.com/mostafa-drz/claude-skills --skill investigate-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigates GitHub Actions failures by fetching recent runs, identifying failures, extracting error logs, and proposing fixes to help teams understand and resolve CI issues.

Core Features & Use Cases

  • Fetches recent workflow runs and statuses for a given repo.
  • Identifies failed jobs, collects relevant logs, and highlights root causes.
  • Suggests concrete remediation steps and alternative investigation paths for quick remediation.

Quick Start

Invoke the /investigate-ci command with a workflow URL, run URL, or repository name to start diagnosing CI failures.

Frequently Asked Questions about investigate-ci

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

FAQPage Schema
How do I diagnose GitHub Actions failures and find the root cause in workflow logs?

To diagnose GitHub Actions failures, you fetch recent workflow runs, identify failed jobs, and extract error logs to pinpoint the root cause. This log-analysis process highlights specific failures and presents actionable remediation steps to resolve the CI issues.

What is the best way to analyze GitHub Actions error logs for a specific repository?

Analyzing GitHub Actions error logs involves fetching recent workflow runs for a repository, identifying failed jobs, and parsing the logs to identify root causes. This approach suggests concrete remediation steps to verify and apply fixes quickly.

Can I investigate CI failures in any GitHub repository without manual log searching?

Yes, you can investigate CI failures in any GitHub repository by providing a workflow URL, run URL, or repository name. The tool automatically fetches recent runs, collects relevant logs, and highlights the root causes of failures.

How do I get actionable remediation steps after a GitHub Actions workflow run fails?

To get actionable remediation steps after a GitHub Actions workflow fails, parse the extracted error logs to identify the root cause. The analysis provides concrete recommendations and alternative investigation paths for quick remediation.

Does this CI investigation approach work with just a workflow URL or run URL?

Yes, this CI investigation approach works with a workflow URL, run URL, or repository name. It uses these inputs to fetch recent workflow statuses, identify failed jobs, and extract the relevant logs for root-cause analysis.