# Analyze CI

> Analyze failed GitHub Action jobs for a pull request.

- Skill: `bishal-pdmsft/analyze-ci-6` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add bishal-pdmsft/analyze-ci-6`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bishal-pdmsft/analyze-ci-6/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bishal-pdMSFT (https://skillmd.com/u/bishal-pdmsft)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/bishal-pdmsft/analyze-ci-6

---


# Analyze CI Failures

This skill analyzes logs from failed GitHub Action jobs using the local agent workflow.

## Prerequisites

- **GitHub Token**: Auto-detected via `gh auth token`, or set `GITHUB_TOKEN` env var

## Usage

```bash
# Analyze all failed jobs in a PR
uv run skills analyze-ci <pr_url>

# Analyze specific job URLs directly
uv run skills analyze-ci <job_url> [job_url ...]

# Show debug info (tokens and costs)
uv run skills analyze-ci <pr_url> --debug
```

Output: A concise failure summary with root cause, error messages, test names, and relevant log snippets.

## Examples

```bash
# Analyze CI failures for a PR
uv run skills analyze-ci https://github.com/mlflow/mlflow/pull/19601

# Analyze specific job URLs directly
uv run skills analyze-ci https://github.com/mlflow/mlflow/actions/runs/12345/job/67890
```


## CI Environment Context Notes

When a failed build looks related to cloud credential bootstrap, networking, or missing runtime identity, include a short environment-reachability checklist in `failed_reasons.txt` before proposing code changes. Common CI checklists mention metadata routes such as `169.254.169.254`, `metadata.google.internal`, `/computeMetadata/v1`, and `/latest/meta-data`, with example `curl` or Python HTTP snippets for reproducing the check. Keep the checklist concise and tied to the observed failure.

