reading-ci-logs

Query GitHub Actions runs, jobs, and check annotations to diagnose PR failures.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jmmL/dr3-old --skill reading-ci-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reading-ci-logs
Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/reading-ci-logs
Command: npx skills add https://github.com/jmmL/dr3-old --skill reading-ci-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers and reviewers quickly diagnose PR failures by extracting and presenting CI/CD results from GitHub without running tests locally.

Core Features & Use Cases

  • CI Run Observation: List recent workflow runs for a repository and identify which runs contain failed jobs.
  • Detailed Failure Insight: Retrieve job status and exact failing steps, with error messages from check annotations for precise debugging.
  • Use Case: A developer pushes a PR and wants to know why the CI checks failed before opening a ticket; this skill surfaces the failure path and relevant logs.

Quick Start

Use the reading-ci-logs skill to fetch the latest PR workflow runs for the repository and inspect any failed jobs and their annotations.

Frequently Asked Questions about reading-ci-logs

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

FAQPage Schema
How do I debug GitHub Actions PR failures without running tests locally?

Debug GitHub Actions PR failures by querying workflow runs, jobs, and check annotations via the GitHub API to retrieve exact failing steps and error messages. This surfaces the failure path and relevant logs directly without local test execution.

How do I retrieve check annotations for failed CI jobs in GitHub Actions?

Retrieve check annotations for failed CI jobs by accessing GitHub API endpoints for workflow runs and jobs, which present concrete failure details including error messages from specific failing steps for precise debugging.

Can I identify which workflow run and step failed in a PR build from GitHub?

Identify which workflow run and step failed in a PR build by listing recent workflow runs for a repository and retrieving job status with exact failing steps. Check annotations provide the precise error messages for diagnosis.

What's the best way to list recent workflow runs and find failed jobs in a repository?

List recent workflow runs and find failed jobs by observing CI run statuses in a repository through the GitHub API. This approach identifies which runs contain failed jobs and extracts the relevant failure details for review.

Does diagnosing CI failures via the GitHub API require local test execution?

Diagnosing CI failures via the GitHub API does not require local test execution. It queries workflow runs, jobs, and check annotations directly to present concrete failure details, enabling rapid diagnosis of PR build failures remotely.

Why should I read CI logs through the GitHub API instead of checking the web UI?

Reading CI logs through the GitHub API extracts and presents CI/CD results programmatically, surfacing exact failing steps and error annotations for precise debugging without manual navigation through the web UI.