agentleFS
CliMACliMA/Oceananigans.jl/.claude/skills/babysit-ci/SKILL.md

babysit-ci

Skill1.4k starsChanged 11 days agoMITView on GitHub

Monitor CI, auto-fix small issues, pause on bigger problems, retrigger flaky runs

  • Commits and pushes

8 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 2 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 2 mentionsSep 2026: 1 mentionOct 2026: 4 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the CliMA/Oceananigans.jl repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about CliMA/Oceananigans.jl

The biggest 5 of 45 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 45

Talked about on GitHub, Bluesky and Hacker News (45 times).

On GitHub · 42

37 more on GitHub

Used with

Projects with it also use addskill, apply-firmware and 10 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.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Check CI status. For each failed job:

    line 27
  2. Distinctive:

    After fixing, commit with a descriptive message and push:

    line 54
  3. Distinctive:

    Stop and explain the problem to the user for any of these:

    line 90
  4. Very specific:

    Always check gh run view <RUN_ID> --log-failed before acting — don't guess from job names alone

    line 117
  5. Very specific:

    After pushing a fix, wait for CI to pick it up before checking again (use gh run list to find the new run)

    line 118
  6. Distinctive:

    Never force-push or rewrite history to fix CI — always add new commits

    line 122

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

Babysit CI

Monitor GitHub Actions CI for the current branch/PR. Auto-fix small issues (typos, missing imports, whitespace, formatting). Pause and describe anything that requires judgment. Retrigger flaky jobs with empty commits.

Step 1: Find the CI Run

# Get the current branch
git branch --show-current

# Find the latest CI run for this branch
gh run list --branch $(git branch --show-current) --limit 5

# Or for a specific PR
gh pr checks <PR_NUMBER>

Step 2: Monitor Loop

Check CI status. For each failed job:

# View the run summary
gh run view <RUN_ID>

# Get logs for a failed job
gh run view <RUN_ID> --log-failed

Step 3: Triage Each Failure

Classify the failure and act accordingly:

Auto-fix (commit and push without asking)

These are mechanical issues with obvious fixes:

FailureHow to fix
Whitespace checkRun .julia/contrib/check-whitespace.jl logic: remove trailing whitespace, ensure final newline, no trailing blank lines
Missing explicit importExplicitImports error in test/unit/quality_assurance.jl — add the missing using/import to the appropriate file
Aqua.jl ambiguitiesAdd the missing method disambiguation
Doctest output mismatchUpdate the expected output in the docstring to match actual output
Typo in error message or docstringFix the typo
Unused import warningRemove the unused import

After fixing, commit with a descriptive message and push:

git add <specific files>
git commit -m "Fix <description of mechanical issue>"
git push

Then continue monitoring from Step 2.

Retrigger (likely flaky)

These failures are often transient and not caused by the PR:

SignalAction
Test passed locally but fails in CIRetrigger
Timeout with no test failureRetrigger
Network/download errorRetrigger
Pkg.instantiate failureRetrigger
CI infrastructure errorRetrigger
A job that failed but is unrelated to the changed filesRetrigger

Retrigger with:

# Re-run just the failed jobs
gh run rerun <RUN_ID> --failed

# Or push an empty commit to retrigger all jobs
git commit --allow-empty -m "Retrigger CI"
git push

Pause and describe (needs judgment)

Stop and explain the problem to the user for any of these:

  • Test logic failure: a test assertion fails (expected vs actual mismatch) that isn't a doctest output update
  • Type instability or GPU error: "dynamic invocation" or similar — may indicate a real bug
  • Regression test failure: numerical results don't match stored references
  • New test failures unrelated to the PR changes: could indicate a flaky test or upstream breakage — explain both possibilities
  • Build failure: package won't precompile or load
  • Multiple interrelated failures: several jobs failing in ways that suggest a common root cause

When pausing, report:

  1. Which job(s) failed
  2. The relevant error output (trimmed to the key lines)
  3. Your assessment of the likely cause
  4. Suggested fix options if you have ideas

Step 4: Confirm All Green

Once all jobs pass:

gh pr checks <PR_NUMBER>

Report the final status to the user.

Notes

  • Always check gh run view <RUN_ID> --log-failed before acting — don't guess from job names alone
  • After pushing a fix, wait for CI to pick it up before checking again (use gh run list to find the new run)
  • The CI workflow has cancel-in-progress for PRs, so a new push cancels the old run automatically
  • CI jobs: Whitespace, test groups (sharding, mpi_tripolar, distributed_output, turbulence_closures, makie, reactant, metal), each running on Julia 1.12
  • Never force-push or rewrite history to fix CI — always add new commits

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.