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
Most recently taken up by
- ryanportfolio/Harness-Firmwaretheir own version, first seen Nov 15, 2026
- ryanportfolio/Corewise.Academytheir own version, first seen Nov 12, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- ryanportfolio/HarnessFirmware.comtheir own version, first seen Nov 5, 2026
- ryanportfolio/STKtheir own version, first seen Oct 20, 2026
- ryanportfolio/savetokenstheir own version, first seen Oct 20, 2026
Who's talking about CliMA/Oceananigans.jl
- @navidcy.bsky.social“This 👇🏼 is open for another 6 days! 🌊 🌏 Not sure if this is for you? Want to find more about the …”Bluesky · Nov 20, 2024 · 21 likes
- @navidcy.bsky.social“Very excited to see our figure on the JFM cover!! large-eddy simulation run with @julialang.org software …”Bluesky · Oct 17, 2025 · 11 likes
- NumericalEarth/NumericalEarth.jl“Clean up `examples/` + create `validation/`”GitHub · Jul 29, 2026 · 3 reactions
- JuliaLang/julia“Package precompilation suddenly hangs on 1.5.4 without direct code changes”GitHub · Apr 13, 2021 · 3 reactions
- NumericalEarth/Breeze.jl“Implement checkpointing for `AtmosphereModel`”GitHub · Feb 27, 2026 · 2 reactions
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
- Jul 29, 2026Clean up `examples/` + create `validation/` — NumericalEarth/NumericalEarth.jl3 reactions · 6 comments
- Apr 13, 2021Package precompilation suddenly hangs on 1.5.4 without direct code changes — JuliaLang/julia3 reactions · 3 comments
- Feb 27, 2026Implement checkpointing for `AtmosphereModel` — NumericalEarth/Breeze.jl2 reactions · 26 comments
- Nov 21, 2025Implement a buoyancy frequency (squared) functionality that is "cloudy-region-aware" — NumericalEarth/Breeze.jl2 reactions · 2 comments
- Sep 13, 2025OceananiganPythonInterface or ClimaOceanPythonInterface auxiliary package for collecting PythonCall utilities? — CliMA/ClimaOcean.jl2 reactions · 5 comments
37 more on GitHub
- Nov 11, 2026Speed up the acoustic substep loop: per-stage factorizations, fewer halo fills, fused damping, batched column solves — NumericalEarth/Breeze.jl1 reaction · 3 comments
- Oct 29, 2026Implement and test checkpointing for biogeochemistry models — OceanBioME/OceanBioME.jl1 reaction
- Oct 20, 2026Test the impact of storing reciprocal metrics — NumericalEarth/Breeze.jl1 reaction · 12 comments
- Oct 16, 2026POCL: reduce launch memory allocations — JuliaGPU/KernelAbstractions.jl1 reaction · 2 comments
- Sep 24, 2026Use Julia 1.13 for Buildkite tests — OceanBioME/OceanBioME.jl1 reaction
- Aug 27, 2026Fix compatibility with Oceananigans v0.110.20 — NumericalEarth/Breeze.jl1 reaction · 3 comments
- Aug 3, 2026Remove dev'd Oceananigans.jl — NumericalEarth/Breeze.jl1 reaction · 1 comment
- Jun 3, 2026Antimeridian-aware `contour`/`contourf` on `GeoAxis` (incl. curvilinear/tripolar grids) — MakieOrg/GeoMakie.jl1 reaction · 1 comment
- Apr 9, 2026Documentation fixes and improvements — NumericalEarth/Terrarium.jl1 reaction · 6 comments
- Apr 2, 2026Implement fast_div using fast rcp — JuliaGPU/CUDA.jl1 reaction · 9 comments
- Jan 30, 2026Update Julia packages to latest version — tomchor/rough-seamounts1 reaction
- Nov 9, 2025Update Oceananigans requirement to 0.100.7 in /docs — NumericalEarth/Breeze.jl1 reaction · 5 comments
- Nov 3, 2025Aliasscope miss-compile for 1.11+ — JuliaGPU/KernelAbstractions.jl1 reaction · 3 comments
- Oct 2, 2025Changes `ExponentialCoordinate` to `ExponentialDiscretization` — CliMA/ClimaOcean.jl1 reaction · 11 comments
- Aug 28, 2025Invalid kernel config generated by `mapreducedim!` with `SubArray` input and output — JuliaGPU/CUDA.jl1 reaction · 3 comments
- Apr 14, 2025Register this package? — JuliaGeo/ConservativeRegridding.jl1 reaction · 5 comments
- Mar 15, 2025[CI] Some improvements to GitHub Actions setup — CliMA/ClimaOcean.jl1 reaction · 5 comments
- Nov 16, 2024Add small (molecular?) background diffusivity on top of Smag-Lilly eddy diffusivity — hdrake/internal-tide-mixing1 reaction · 2 comments
- Dec 8, 2022Check if NetCDF_jll `is_available` before loading code — JuliaGeo/NCDatasets.jl1 reaction · 3 comments
- Jul 8, 2021Detect common integer exponentiations and handle them directly. — JuliaGPU/CUDA.jl1 reaction · 3 comments
- May 21, 2021Error when computing reductions into a view with `reduce_blocks > 1` — JuliaGPU/CUDA.jl1 reaction · 6 comments
- Mar 5, 2021Using joblib to parallelize plotting — jbusecke/xmovie1 reaction · 8 comments
- Jul 2, 2020Make Ref pass by-reference — JuliaGPU/CUDA.jl1 reaction · 5 comments
- Oct 21, 2026Update Oceananigans requirement from 0.113 to 0.113, 0.114 in /test — aria-verify/Assimilate.jl0 reactions
- Mar 13, 2026Make docs build faster by running examples in parallel — CliMA/CloudMicrophysics.jl0 reactions
- Feb 19, 2026STATUS: Differentiating Breeze — NumericalEarth/Breeze.jl0 reactions
- Jan 16, 2026Overlay methods on top of CUDA.jl method table — EnzymeAD/Reactant.jl0 reactions · 1 comment
- Nov 10, 2025Open boundary conditions with boundary mass flux correction — NumericalEarth/Breeze.jl0 reactions · 1 comment
- Aug 6, 2025Support Julia LTS version — googlecolab/colabtools0 reactions · 2 comments
- Jul 15, 2025Version and thread check at init — fesmc/Pagos.jl0 reactions
- Jun 16, 2025Error in ECCO dataset download — CliMA/ClimaOcean.jl0 reactions · 30 comments
- Apr 23, 2025Test with new weno reconstruction — simone-silvestri/NVIDIA_benchmark_tests0 reactions · 1 comment
- Sep 27, 2023Have we tried using `Field` as boundary condition? — yuchenma23/RT_tracer0 reactions
- Jun 13, 2022Use `.dataset` rather than `.field_time_serieses`? — CliMA/ParameterEstimocean.jl0 reactions · 1 comment
- Mar 9, 2022Can saved output be improved? — navidcy/mesoscale-parametrization0 reactions · 5 comments
- Feb 7, 2022Oceananigans.jl ocean modeling example — ClimateMARGO/interactive0 reactions · 4 comments
- Sep 27, 2020Milestones until we can submit a JOSS paper? — ali-ramadhan/Atmosfoolery.jl0 reactions · 2 comments
On Bluesky · 2
- Nov 20, 2024This 👇🏼 is open for another 6 days! 🌊 🌏 Not sure if this is for you? Want to find more about the project? Are you on the fence? Do… — @navidcy.bsky.social21 likes and reposts
- Oct 17, 2025Very excited to see our figure on the JFM cover!! large-eddy simulation run with @julialang.org software Oceananigans.jl;… — @navidcy.bsky.social11 likes and reposts
On Hacker News · 1
- May 26, 2020Oceananigans.jl: fast and friendly fluid dynamics on CPUs and GPUs2 points
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.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-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
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- NumericalEarth/Breeze.jl★ 9068% same
Wrote their own version · 7
- xmtplabs/convos-ios★ 16same name
- ryanportfolio/winuse-mcp★ 2same name
- ryanportfolio/Corewise.Academy★ 1same name
- ryanportfolio/Harness-Firmware★ 1same name
- ryanportfolio/savetokens★ 1same name
- ryanportfolio/STK★ 1same name
- ryanportfolio/HarnessFirmware.com★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-featureSkill
- build-docsSkill
- new-simulationSkill
- run-testsSkill
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
- Distinctive: line 27
Check CI status. For each failed job:
- Distinctive: line 54
After fixing, commit with a descriptive message and push:
- Distinctive: line 90
Stop and explain the problem to the user for any of these:
- Very specific: line 117
Always check gh run view <RUN_ID> --log-failed before acting — don't guess from job names alone
- Very specific: line 118
After pushing a fix, wait for CI to pick it up before checking again (use gh run list to find the new run)
- Distinctive: line 122
Never force-push or rewrite history to fix CI — always add new commits
“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.
Files
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-failedStep 3: Triage Each Failure
Classify the failure and act accordingly:
Auto-fix (commit and push without asking)
These are mechanical issues with obvious fixes:
| Failure | How to fix |
| Whitespace check | Run .julia/contrib/check-whitespace.jl logic: remove trailing whitespace, ensure final newline, no trailing blank lines |
| Missing explicit import | ExplicitImports error in test/unit/quality_assurance.jl — add the missing using/import to the appropriate file |
| Aqua.jl ambiguities | Add the missing method disambiguation |
| Doctest output mismatch | Update the expected output in the docstring to match actual output |
| Typo in error message or docstring | Fix the typo |
| Unused import warning | Remove 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 pushThen continue monitoring from Step 2.
Retrigger (likely flaky)
These failures are often transient and not caused by the PR:
| Signal | Action |
| Test passed locally but fails in CI | Retrigger |
| Timeout with no test failure | Retrigger |
| Network/download error | Retrigger |
Pkg.instantiate failure | Retrigger |
| CI infrastructure error | Retrigger |
| A job that failed but is unrelated to the changed files | Retrigger |
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 pushPause 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:
- Which job(s) failed
- The relevant error output (trimmed to the key lines)
- Your assessment of the likely cause
- 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-failedbefore 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 listto find the new run) - The CI workflow has
cancel-in-progressfor 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
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
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.

