skills.rest
orekyuu
orekyuuCOMMUNITY
Explore all skills by this author →
Website𝕏@orekyuuGitHub

investigate-ci-failure

Identify CI runs and delegate log analysis to a sub-agent.

Updated Feb 28, 2026
Search Tags:#automation#debugging#troubleshooting#logs#github actions#ci
One-click install
npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill investigate-ci-failure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate-ci-failure
Source: https://github.com/orekyuu/orekyuu-claude-plugins/tree/main/plugins/gh-tools/skills/investigate-ci-failure
Command: npx skills add https://github.com/orekyuu/orekyuu-claude-plugins --skill investigate-ci-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand and diagnose why a Continuous Integration (CI) pipeline has failed, saving valuable debugging time.

Core Features & Use Cases

  • Automated Run Identification: Automatically finds the relevant CI run based on PR number or current branch.
  • Log Analysis Delegation: Leverages a sub-agent to perform in-depth log analysis, conserving main context.
  • Use Case: When your GitHub Actions pipeline fails, you can use this skill to pinpoint the exact run, analyze its logs, and get a summary of the root cause.

Quick Start

Use the investigate-ci-failure skill to analyze the latest CI failure on the current branch.

Frequently Asked Questions about investigate-ci-failure

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

FAQPage Schema
How do I debug GitHub Actions CI failures automatically?▼

Automated CI failure analysis identifies the relevant GitHub Actions run using a PR number, run ID, or the current branch, then delegates log parsing to a sub-agent to summarize the root cause.

What is the best way to analyze CI logs for a specific pull request?▼

Analyzing CI logs for a specific pull request is handled by identifying the corresponding CI run via the PR number. The skill then delegates the log parsing to a sub-agent to conserve the main context and provide a root cause summary.

Do I need GitHub CLI installed to troubleshoot CI pipeline issues?▼

Yes, you need the GitHub CLI installed to troubleshoot CI pipeline issues with this approach. The skill requires GitHub CLI to query and identify the relevant CI run, alongside the Agent tool for sub-agent execution.

Can I find failed GitHub Actions runs without an explicit run ID?▼

Yes, you can find failed GitHub Actions runs without an explicit run ID. The skill automatically defaults to the current branch's latest failure or can locate the run using a PR number if an explicit run ID is not provided.

Why does CI troubleshooting fail to find my GitHub Actions run?▼

CI troubleshooting may fail to find your GitHub Actions run if the GitHub CLI is not installed or authenticated properly, or if the specified PR number and current branch lack any associated failed CI runs.

Related Skills

Explore More Software Engineering Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
simonwjacksonsimonwjackson

se-debug

Trace causal chains from trigger to symptom to confirm root causes.

Community
Advanced
GarrettRoiGarrettRoi

github-repo-management

Manage GitHub repositories via CLI tools and the REST API.

Community
Advanced
sk8metalmesk8metalme
1

ci-cd

Diagnose CI/CD failures by inspecting full GitHub Actions and Screwdriver logs.

Community
Advanced