fix-ci SKILL.md skillA

fix-ci from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add khaledsaeed18/dotclaude/fix-ci@git:20260921.b1a4652

Pins git:20260921.b1a4652 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

khaledsaeed18/dotclaude

Path

.claude-plugin/plugins/engineering/skills/fix-ci/SKILL.md

Versions recorded

2

Latest version

git:20260921.b1a4652, committed Sep 21, 2026

First version recorded

Jul 4, 2026

Size

3,163 bytes

Repository stars

5

License

MIT

Diagnose and fix a failing CI run by pulling the actual failure logs (gh run view --log-failed), reproducing the failure locally, fixing the root cause rather than the symptom, and verifying green before and after pushing. Use when a GitHub Actions run is red, a PR check is failing, or CI passes locally but fails remotely.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

Fix the failure CI actually reported, not the one you assume it hit. The log line that failed the job is evidence; everything else is guessing. Pull it first, reproduce it locally second, and only then change code.

## Step 1: Get the real failure

```bash
# What failed, and on which commit
gh run list --limit 10
gh run view <run-id> --log-failed 2>&1 | tail -80
```

Read the failed step's output completely. Identify: the failing step name, the exact error, and whether the failure is in *your change* or in the pipeline itself (setup step, cache, runner image, flaky network). If several jobs failed, find the first failure in dependency order; downstream jobs often fail as a consequence.

If the run belongs to a PR, also check which check is required and whether the failure is new to this branch:

```bash
gh pr checks <pr-number>
git log --oneline origin/main..HEAD
```

## Step 2: Reproduce locally

Run the failing step's actual command from the workflow file, not your usual local equivalent:

```bash
# Read the workflow to get the exact command and environment
cat .github/workflows/<workflow>.yml
```
…

Read the whole file at its exact version.

How to install

mdr add khaledsaeed18/dotclaude/fix-ci@sha256:5ffd1bf88db59dd7

[![mdr](https://markdownregistry.com/badge/art_neqfpshcn24n6oqr.svg)](https://markdownregistry.com/a/art_neqfpshcn24n6oqr)

Versions

The registry has recorded 2 versions of this file, between Jul 4, 2026 and Sep 21, 2026, about one every 80 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_neqfpshcn24n6oqr
GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/fix-ci
GET https://markdownregistry.com/api/v1/blob/5ffd1bf88db59dd73b95e14ff2ae80922cb1c51d59098868f4a2afb1167a550e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from khaledsaeed18/dotclaude

Every file in khaledsaeed18/dotclaude

Other files named fix-ci

Browse by kind, by grade A, or by owner.