agentleFS
NumericalEarthNumericalEarth/Breeze.jl/.claude/skills/run-tests/SKILL.md

run-tests

Skill90 starsChanged 3 months agoApache-2.0View on GitHub

Run targeted Breeze tests, prioritized by what's likely to break

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

Adopted by

Most recently taken up by

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.
  • ShopifySkill

    prepare-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

  • 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 4 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 4 projects that use this

  • MicrosoftSkill

    release

    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

  • GoogleSkill

    code-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

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 4

    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. Distinctive:

    Run targeted tests one-by-one, prioritized by what's most likely to fail given recent changes.

    line 8
  2. Distinctive:

    Never run the full test suite blindly — it's too large.

    line 9
  3. Distinctive:

    Look at the recent changes (staged, unstaged, or recent commits) and determine which test files are most likely affected.

    line 13
  4. Very specific:

    Every test/<name>.jl is a valid test_args name.

    line 42
  5. Distinctive:

    If a test fails, fix the issue

    line 56
  6. Very specific:

    After direct tests pass, run quality_assurance to catch import/doctest issues

    line 59
  7. Very specific:

    If Julia version issues arise, delete Manifest.toml and run Pkg.instantiate()

    line 66

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

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 areaTest files to run first
src/AtmosphereModels/atmosphere_model_construction, set_atmosphere_model, dynamics
src/AtmosphereModels/atmosphere_model.jlatmosphere_model_construction
src/AtmosphereModels/update_*.jldynamics, set_atmosphere_model
src/AtmosphereModels/microphysics_interface.jlcloud_microphysics_1M, cloud_microphysics_2M, saturation_adjustment
src/AnelasticEquations/anelastic_pressure_solver_analytic, anelastic_pressure_solver_nonhydrostatic, dynamics
src/CompressibleEquations/acoustic_substepping_components, acoustic_substepping_open_boundaries, acoustic_substepping_stability, dynamics
src/StaticEnergyFormulations/, src/PotentialTemperatureFormulations/dynamics, set_atmosphere_model, moist_state_conversion
src/Thermodynamics/saturation_adjustment, unit_tests, reference_states
src/Solvers.jlsolvers, saturation_adjustment
src/TurbulenceClosures/turbulence_closures, vertical_diffusion, tke_closure
src/Microphysics/cloud_microphysics_1M, cloud_microphysics_2M, saturation_adjustment
src/Microphysics/ (P3)predicted_particle_properties_processes, p3_reference_process_routing
src/Advection.jldynamics, tracer_dynamics, advection_schemes
src/Forcings/forcing_and_boundary_conditions, geostrophic_subsidence_forcings, specific_forcing
src/BoundaryConditions/forcing_and_boundary_conditions, boundary_conditions
src/TimeSteppers/dynamics, runge_kutta_stage_times, acoustic_substepping_stability
src/TerrainFollowingDiscretization/terrain_following_metrics, terrain_following_reference_state, terrain_following_split_explicit
src/KinematicDriver/kinematic_driver
src/ParcelModels/parcel_dynamics
src/single_column_mode.jlsingle_column_mode
src/Breeze.jl (exports)quality_assurance
Docstringsdoctests
Radiation (ext/)gray_radiative_transfer, clear_sky_radiative_transfer, all_sky_radiative_transfer, radiation_scheduling

Every test/<name>.jl is a valid test_args name; ls test/ lists them all.

Step 2: Run the Most Likely Test First

julia --project -e '
using Pkg
ENV["CUDA_VISIBLE_DEVICES"] = "-1"
Pkg.test("Breeze"; test_args=`atmosphere_model_construction`)
'

Step 3: Fix and Iterate

  1. If a test fails, fix the issue
  2. Re-run the same test to confirm the fix
  3. Move on to the next most likely test
  4. After direct tests pass, run quality_assurance to catch import/doctest issues

Notes

  • GPU tests may fail with "dynamic invocation error" — always test on CPU first
  • quality_assurance checks explicit imports and Aqua.jl quality — run this for any change
  • Reactant tests require --check-bounds=auto and Julia < 1.12
  • If Julia version issues arise, delete Manifest.toml and run Pkg.instantiate()

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.