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

fix-ci

Skill8 starsChanged 3 months agoMITView on GitHub

Diagnose and fix failing CI checks on the current branch

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, create-pr and 7 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

    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

  • +1 more from getsentry

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a PR number is given ($ARGUMENTS), check that PR's CI status:

    line 13
  2. Distinctive:

    Read the error output carefully.

    line 30
  3. Distinctive:

    Test failure: read the failing test, understand what it asserts, read the code it tests

    line 32
  4. Distinctive:

    After fixing, verify locally:

    line 42
  5. Distinctive:

    Run the same check that failed (build, test, lint, typecheck)

    line 43
  6. Distinctive:

    If the fix introduced new failures, fix those too

    line 45

“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 Failing CI

Diagnose and fix CI failures autonomously. No hand-holding needed.

Step 1: Identify the Failure

If a PR number is given ($ARGUMENTS), check that PR's CI status:

gh pr checks "$ARGUMENTS" --json name,state,link

Otherwise check the current branch:

gh run list --branch "$(git symbolic-ref --short HEAD)" --limit 5 --json status,conclusion,name,databaseId

Find the most recent failing run and get its logs:

gh run view <RUN_ID> --log-failed

Step 2: Diagnose

Read the error output carefully. Common categories:

  • Build failure: type errors, missing imports, syntax errors
  • Test failure: read the failing test, understand what it asserts, read the code it tests
  • Lint failure: style violations, unused imports
  • Type check failure: TypeScript errors

For each failure, find and read the relevant source file to understand context.

Step 3: Fix

Make the minimal fix for each failure. Do not refactor surrounding code. Do not add features.

After fixing, verify locally:

  1. Run the same check that failed (build, test, lint, typecheck)
  2. Confirm it passes
  3. If the fix introduced new failures, fix those too

Step 4: Commit and Push

Stage only the files you changed. Commit with a clear message:

fix: resolve CI failure in <what failed>

<one line explaining the root cause>

Push to the current branch. If a PR number was given, report the fix on the PR.

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