agentleFS
Sign inStart free
digitaltracerdigitaltracer/agent-skills/skills/fix-ci/SKILL.md

fix-ci

Skill4 starsChanged yesterdayMITView on GitHub

Diagnose and fix a failing GitHub Actions run. Use when given an Actions run URL, when CI checks on a PR are failing, or after a push to babysit checks until green.

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use get-pr-comments, create-pr and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jaydubya818Skill

    get-pr-comments

    Use when pull-request feedback needs to be fetched and summarized for action.

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 10 projects that use this

  • MicrosoftSkill

    merge

    Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 4 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Monorepos: if the fix applies to one service's workflow or dependency pins, check every sibling service for the same defect and fix them in …

    line 24
  2. Distinctive:

    Commit atomically. Push only with explicit permission — then watch until green:

    line 25
  3. Distinctive:

    Keep stable CI facts (actions role names, private-index auth, service lists, Python version splits) in the project's CLAUDE.md so they …

    line 35

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fix CI

Argument: an Actions run URL, a PR number, or nothing (use the latest failing run on the current branch).

Diagnose

  1. Resolve the run: from the URL, or gh run list --branch $(git branch --show-current) --limit 5.
  2. gh run view <id> --log-failed — read the actual failing step output, not just the job name.
  3. Cross-reference working examples before inventing a fix. Two sources answer most CI questions:
    • Other workflows in the same repo that already solve the problem (e.g. deployment workflows that already authenticate to the registry/CodeArtifact — copy how they get their token).
    • The last green run of this same workflow: gh run list --workflow <name> --status success --limit 3, then diff what changed since.
  4. Distinguish the failure class: is the code/test wrong, or the way CI runs it wrong? When local and CI disagree (e.g. ruff formats locally but fails in CI), compare tool versions and config resolution first.

Fix

  • Minimal and targeted. Fix the failing thing; do not restructure the workflow unprompted.
  • Monorepos: if the fix applies to one service's workflow or dependency pins, check every sibling service for the same defect and fix them in the same pass — a partial sweep is the known failure mode.
  • Commit atomically. Push only with explicit permission — then watch until green:
gh run watch <id> --exit-status || gh run view <id> --log-failed

Repeat diagnose→fix→push until the run passes. Report the final status plainly, including any steps that remain red.

Per-repo facts

Keep stable CI facts (actions role names, private-index auth, service lists, Python version splits) in the project's CLAUDE.md so they don't need rediscovering. If this skill uncovers such a fact the project CLAUDE.md lacks, offer to add it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free