Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
A skill your agent uses when choosing or running JET tests after code changes.
Install Run Test
$ npx skills add aviatesk/JET.jl --skill run-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aviatesk/JET.jl run-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-test .claude/skills/run-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .claude/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aviatesk/JET.jl --skill run-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aviatesk/JET.jl run-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/run-test .agents/skills/run-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .agents/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aviatesk/JET.jl --skill run-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aviatesk/JET.jl run-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/run-test .cursor/skills/run-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .cursor/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aviatesk/JET.jl.git --path .agents/skills/run-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aviatesk/JET.jl --skill run-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aviatesk/JET.jl run-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/run-test .gemini/skills/run-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .gemini/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aviatesk/JET.jl run-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aviatesk/JET.jl --skill run-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/run-test .github/skills/run-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .github/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aviatesk/JET.jl --skill run-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aviatesk/JET.jl run-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviatesk/JET.jl.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/run-test .opencode/skills/run-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-test" agent skill from https://github.com/aviatesk/JET.jl/tree/master/.agents/skills/run-test into .opencode/skills/run-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-test- GitHub stars
- 883
- Token cost
- ~643 tokens
- SKILL.md length
- 262 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when choosing or running JET tests after code changes.
- Running JET tests after code changes
- SKILL.md covers Choose the narrowest useful test, Focused iteration with…, Full-suite validation and Environment failures, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Run Test is an agent skill from aviatesk/JET.jl. 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.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: A code analyzer for Julia. No need for additional type annotations. The licence is MIT.
When your agent uses it
- Running JET tests after code changes
Example prompts
- “/run-test”
What it can do on your machine
Read from SKILL.md and the folder at commit 19c3b4c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Run Test loads about 643 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 262 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aviatesk/JET.jl at commit 19c3b4c, republished under its MIT licence (© aviatesk). 262 words, ~643 tokens.
Download SKILL.mdSave it as
.claude/skills/run-test/SKILL.md (or your agent's skills folder).- name
- run-test
- description
- 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.
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.
© aviatesk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/run-test of aviatesk/JET.jl.
Open the folder on GitHubat commit 19c3b4c
Compare with similar skills
Run Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run Test this skillaviatesk/JET.jl | 883 | — | ~643 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from aviatesk/JET.jl
Commit
aviatesk/JET.jl
A skill your agent uses when writing a commit message, and MUST invoke before creating any git commit.
Write Test
aviatesk/JET.jl
A skill your agent uses when adding or modifying JET tests. An agent skill from aviatesk/JET.jl.
Changelog
aviatesk/JET.jl
Invoke before committing user-facing JET changes such as features, bug fixes, compatibility changes, or deprecations.
Related
Categories
Questions about Run Test
What does Run Test do?
A skill your agent uses when choosing or running JET tests after code changes. jl. Use when choosing or running JET tests after code changes.
When should I use Run Test?
Run Test fits situations like: running JET tests after code changes.
How do I install Run Test in Claude Code?
Run `npx skills add aviatesk/JET.jl --skill run-test -a claude-code`. Or copy the skill folder (.agents/skills/run-test in aviatesk/JET.jl) into .claude/skills/run-test in your project. Claude Code loads it when a task matches its description.
How do I install Run Test in Codex?
Run `npx skills add aviatesk/JET.jl --skill run-test -a codex`. Or copy the skill folder (.agents/skills/run-test in aviatesk/JET.jl) into .agents/skills/run-test in your project. Codex loads it when a task matches its description.
Can I use Run Test in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aviatesk/JET.jl --skill run-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-test, .gemini/skills/run-test, .github/skills/run-test and .opencode/skills/run-test in your project.
What does Run Test need to run?
SKILL.md names no scripts, command-line tools or credentials: Run Test is instructions for the agent only.
Does Run Test access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Run Test safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Run Test use?
Run Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Run Test use?
About 643 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Run Test?
Skills that share tags, products or a category with Run Test: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run Test?
aviatesk (a GitHub user) maintains it in aviatesk/JET.jl, which has 883 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: aviatesk/JET.jl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.