agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/fix-ci/SKILL.md

fix-ci

Skill1 starsChanged 41 days agoMITView on GitHub

Diagnose and fix failing CI checks. Use when pipelines fail, PR checks are red, or the user asks to fix CI/CD.

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use get-pr-comments, merge and 3 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

  • 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

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 10 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

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

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 4

    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:

    Read the failure log from the error upward to the first root cause.

    line 11
  2. Distinctive:

    Prefer minimal fixes scoped to the failure.

    line 35
  3. Distinctive:

    Do not disable tests or weaken CI unless the user explicitly asks.

    line 36
  4. Distinctive:

    If flaky and unowned, document flake evidence and a follow-up.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 37 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

Process

  1. Identify the exact failing job and step.
  2. Read the failure log from the error upward to the first root cause.
  3. Reproduce locally with the same command when possible.
  4. Fix the cause, not the symptom (avoid skipping checks).
  5. Re-run the failing check; confirm green before stopping.

Common Causes

  • Flaky tests → stabilize assertions/timing; do not blind-retry forever
  • Env/secrets missing → document required vars; do not hardcode secrets
  • Lockfile drift → regenerate with the project’s package manager
  • Version skew → match CI toolchain versions
  • Permissions / path issues → fix paths and checkout assumptions

Output

Failing check: ...
Root cause: ...
Fix: ...
Verification: <command> → pass

Rules

  • Prefer minimal fixes scoped to the failure.
  • Do not disable tests or weaken CI unless the user explicitly asks.
  • If flaky and unowned, document flake evidence and a follow-up.

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