agentleFS
Sign inStart free
ShipfoxHQShipfoxHQ/shipfox/.agents/skills/fix-ci/SKILL.md

fix-ci

Skill87 starsChanged 12 days agoMITView on GitHub

Diagnose and fix failing CI checks on a pull request, then commit and push the fix. Trigger on /fix-ci, fix CI, CI is red, checks are failing, or fix the failing build on a PR.

  • Commits and pushes

44 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 5 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

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 42 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use the returned number in every later command.

    line 21
  2. Distinctive:

    If checks are still running, wait for them.

    line 26
  3. Distinctive:

    Read the failure from the job log.

    line 44
  4. Very specific:

    If the failure is unrelated to the diff, such as a known flaky test or an infrastructure error, rerun the failed GitHub Actions jobs …

    line 57
  5. Very specific:

    Commit the fix through the commit skill and push with git push.

    line 66

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

Find why a pull request's checks fail, fix the cause, and push the fix.

Input

/fix-ci [pr]

[pr] is a pull request number or URL. Without it, omit <pr> below to use the pull request for the current branch:

gh pr view <pr> --json number,url,headRefName

Use the returned number in every later command. If the current branch is not headRefName, run gh pr checkout <number>.

Process

  1. If checks are still running, wait for them. CI can outlast a shell command timeout, so run the command in the background or run it again until it exits:

    gh pr checks <number> --watch --interval 30

  2. List the failed checks:

    gh pr checks <number> --json name,bucket,link --jq '.[] | select(.bucket == "fail")'

    A GitHub Actions link has the form .../actions/runs/<run-id>/job/<job-id>. For other checks, such as Vercel, open the link to read the failure. If nothing failed, report that and stop.

  3. Read the failure from the job log. For E2E failures, download the diagnostics artifact before you form a theory:

    gh run view <run-id> --job <job-id> --log-failed
gh run download <run-id> -p 'e2e-diagnostics*' -D .context/ci/<run-id>
  4. Reproduce the failure locally with the matching turbo task and package filter. Read the local development and release workflow to pick the task.
  5. Fix the cause. Do not skip, weaken, or delete a test to make it pass.

  6. If the failure is unrelated to the diff, such as a known flaky test or an infrastructure error, rerun the failed GitHub Actions jobs instead of changing code. Rerun only when gh run view <run-id> --json attempt reports attempt 1. For other checks, report the failure instead:

    gh run rerun <run-id> --failed
  7. Commit the fix through the commit skill and push with git push.

Report

Report each failed check with its cause and outcome: fixed in a commit, rerun as unrelated, or not fixed with the reason. Include the commit hashes pushed.

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