run-tests
Skill1.4k starsChanged 10 days agoMITView on GitHub
Run targeted Oceananigans tests, prioritized by what's likely to break
48 other projects use a version of this, 1 of them edited.
Trending
More talk lately.about the whole repository
Most recently taken up by
- utopia-rise/fmod-gdextensiontheir own version, first seen Nov 9, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- coralogix/cx-clitheir own version, first seen Nov 8, 2026
- DataDog/dd-trace-pytheir own version, first seen Nov 1, 2026
- busycaesar/Harnesstheir own version, first seen Nov 1, 2026
- NumericalEarth/Breeze.jledited, first seen Oct 17, 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 prepare-release, create-pr 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.
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 3 projects that use this
SentrySkillcreate-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 4 projects that use this
SentrySkillcommit
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 4 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 5 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 5 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- NumericalEarth/Breeze.jl★ 9035% same
Wrote their own version · 47
- netbox-community/netbox★ 22ksame name
- yagop/node-telegram-bot-api★ 9.2ksame name
- gitextensions/gitextensions★ 8.6ksame name
- ethereum/consensus-specs★ 4ksame name
- dotnet/sdk★ 3.2ksame name
- ComplianceAsCode/content★ 2.8ksame name
- idaholab/moose★ 2.4ksame name
- microsoft/testfx★ 1.1ksame name
- serenedb/serenedb★ 965same name
- utopia-rise/fmod-gdextension★ 954same name
37 more not listed
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
- babysit-ciSkill
- build-docsSkill
- new-simulationSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
5
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
- Distinctive: line 8
Run targeted tests one-by-one, prioritized by what's most likely to fail given recent changes.
- Distinctive: line 9
Never run the full test suite blindly — it's too large.
- Distinctive: line 13
Look at the recent changes (staged, unstaged, or recent commits) and determine which test files are most likely affected.
- Distinctive: line 43
Run a single test file on CPU:
- Distinctive: line 72
If a test fails, fix the issue
- Very specific: line 75
After direct tests pass, run unit/quality_assurance to catch import/doctest issues
- Very specific: line 82
If Julia version issues arise, delete Manifest.toml and run Pkg.instantiate()
“Common” is measured: kept by at least 6 in 10 of the 44 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
Run Tests
Run targeted tests one-by-one, prioritized by what's most likely to fail given recent changes. Never run the full test suite blindly — it's too large. Fix each failure before moving on.
Step 1: Identify What Changed
Look at the recent changes (staged, unstaged, or recent commits) and determine which test files are most likely affected. Use this mapping:
| Changed area | Tests to run first (group/name = test/group/name.jl) |
src/Grids/ | unit/grids, unit/grid_reconstruction |
src/Fields/ | unit/field, abstract_operations/computed_field, unit/field_scans |
src/Operators/ | unit/operators, unit/vector_rotation |
src/BoundaryConditions/ | unit/boundary_conditions, time_stepping/boundary_conditions |
src/Models/NonhydrostaticModels/ | time_stepping/nonhydrostatic_models, time_stepping/time_stepping |
src/Models/HydrostaticFreeSurfaceModels/ | hydrostatic_free_surface/models, hydrostatic_free_surface/split_explicit_solver |
src/Models/ShallowWaterModels/ | shallow_water/models |
src/TimeSteppers/ | time_stepping/time_stepping, time_stepping/dynamics |
src/TurbulenceClosures/ | turbulence_closures/turbulence_closures |
src/Advection/ | time_stepping/immersed_advection, time_stepping/dynamics |
src/BuoyancyFormulations/ | unit/buoyancy, time_stepping/seawater_density |
src/Solvers/ | poisson_solvers/regular_grids, general_solvers/batched_tridiagonal |
src/Simulations/ | simulation/simulations, simulation/diagnostics |
src/OutputWriters/ | simulation/output_writers, simulation/jld2_writer, simulation/netcdf_writer |
src/OutputReaders/ | simulation/output_readers |
src/ImmersedBoundaries/ | unit/immersed_boundary_grid, hydrostatic_free_surface/immersed_boundaries |
src/Coriolis/ | coriolis/coriolis |
src/Forcings/ | time_stepping/forcings |
src/Oceananigans.jl (exports) | unit/quality_assurance |
Docstrings, docs/src pages | doctests/doctests (GPU only), unit/quality_assurance |
ext/ (extensions) | Corresponding <extension>/<extension> (e.g. makie/makie, metal/metal) |
Step 2: Run the Most Likely Test First
Tests are selected by a prefix of their group/name and run in parallel worker processes.
Run a single test file on CPU:
CUDA_VISIBLE_DEVICES=-1 TEST_ARCHITECTURE=CPU julia --project -e '
using Pkg
Pkg.test("Oceananigans"; test_args=["unit/grids"])
'Or run a whole group if the changes span multiple areas:
CUDA_VISIBLE_DEVICES=-1 TEST_ARCHITECTURE=CPU julia --project -e '
using Pkg
Pkg.test("Oceananigans"; test_args=["unit", "--jobs=4", "--verbose"])
'Pkg.test(; test_args=["--list"]) prints every test with its last measured duration. The
groups are the directories under test/: unit, abstract_operations, coriolis,
tripolar_grid, poisson_solvers, general_solvers, turbulence_closures, time_stepping,
regression, hydrostatic_free_surface, vertical_coordinate, shallow_water, simulation,
lagrangian_particles, multi_region, conservative_regridding, scripts, memory_allocation,
init; and, only when selected explicitly, distributed, enzyme, reactant, sharding,
metal, amdgpu, oneapi, makie, convergence. TEST_GROUP=unit is equivalent to
test_args=["unit"].
Step 3: Fix and Iterate
- If a test fails, fix the issue
- Re-run the same test to confirm the fix
- Move on to the next most likely test
- After direct tests pass, run
unit/quality_assuranceto catch import/doctest issues
Notes
- GPU tests may fail with "dynamic invocation error" — always test on CPU first
unit/quality_assurancechecks explicit imports and Aqua.jl quality — run this for any changetest/mpi/tests need 4 MPI ranks (MPI_TEST=true mpiexec -n 4 julia --project -e 'using Pkg; Pkg.test()'withTEST_GROUP=distributed) — skip unless changes touchsrc/DistributedComputations/- If Julia version issues arise, delete
Manifest.tomland runPkg.instantiate()
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.

