run-test
Skill884 starsChanged 4 months agoMITView on GitHub
Use when choosing or running JET tests after code changes. Prefer the most specific relevant test, use TestRunner for focused iteration, and reserve the full suite for broad validation.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- mx-space/coretheir own version, first seen Nov 14, 2026
- UI5/openui5their own version, first seen Oct 8, 2026
- aviatesk/JETLS.jledited, first seen Oct 8, 2026
- apache/pinottheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- aviatesk/JETLS.jl★ 31911% same
Wrote their own version · 3
- apache/pinot★ 6.2ksame name
- UI5/openui5★ 3.3ksame name
- mx-space/core★ 567same 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- changelogSkill
- commitSkill
- write-testSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill when validating JET changes or deciding which test command to run.
- Very specific: line 16
If the user names a test file or testset, run it first.
- Distinctive: line 28
Run commands from the repository root so relative paths and the workspace resolve correctly.
- Very specific: line 39
Follow test/runtests.jl rather than assuming every test has a root-level path.
- Very specific: line 43
When testrunner --help succeeds and the target @testset is clear, use TestRunner.jl for faster iteration:
- Distinctive: line 57
Avoid the full suite unless:
- Distinctive: line 61
No narrower test provides sufficient coverage.
- Distinctive: line 63
Use the package test lifecycle when matching CI or performing final broad validation:
- Very specific: line 78
If a failure looks environment-related, first confirm that the command ran from the repository root.
“Common” is measured: kept by at least 6 in 10 of the 3 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 JET tests
Use this skill when validating JET changes or deciding which test command to run.
Choose the narrowest useful test
If the user names a test file or testset, run it first. Otherwise, use
test/runtests.jl and nearby tests to identify the
smallest relevant target.
Most test files can run independently. For example:
julia --startup-file=no --project=test test/ui/test_print.jl--startup-file=noavoids loading unrelated startup utilities.--project=testselects JET's test environment and its dependencies.- Run commands from the repository root so relative paths and the workspace resolve correctly.
JET tests are organized by component. Common locations include:
test/abstractinterpret/test/analyzers/test/toplevel/test/ui/
There are also integration and miscellaneous tests directly under test/.
Follow test/runtests.jl rather than assuming every test has a root-level path.
Focused iteration with TestRunner.jl
When testrunner --help succeeds and the target @testset is clear, use
TestRunner.jl for faster iteration:
testrunner --project=test \
test/toplevel/test_virtualprocess.jl \
"syntax error reports"TestRunner.jl is experimental. If it fails for a TestRunner-specific reason, fall back to running the complete test file independently.
Full-suite validation
Avoid the full suite unless:
- Changes affect multiple components or shared compiler infrastructure.
- The user explicitly requests it.
- No narrower test provides sufficient coverage.
Use the package test lifecycle when matching CI or performing final broad validation:
julia --startup-file=no -e 'using Pkg; Pkg.test()'JET's workspace also supports running test/runtests.jl directly:
julia --startup-file=no --project=test test/runtests.jlEnvironment failures
If a failure looks environment-related, first confirm that the command ran from
the repository root. Do not modify Project.toml or test/Project.toml to fix
the environment. Report the unresolved failure and ask the user for guidance.
Reporting
In the final response, report the exact command that ran and whether it passed, failed, or timed out. If tests were skipped, explain why.
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.

