Build and run the unit tests covering changed Celeritas source files.

Custom licenceAuto-check passedTesting & QA

Install Test Change

skills CLI
$ npx skills add celeritas-project/celeritas --skill test-change -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install celeritas-project/celeritas test-change --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/celeritas-project/celeritas.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/test-change .claude/skills/test-change && rm -rf skills-src

Use ~/.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/

Facts

Skill name
test-change
GitHub stars
105
Token cost
~640 tokens
SKILL.md length
281 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Custom licence

At a glance

Build and run the unit tests covering changed Celeritas source files.

  • Works in 4 steps: Pick a build directory → Map changed files to tests → Build and run → …
  • Tasks that involve Unit testing
  • SKILL.md covers 1. Pick a build directory, 2. Map changed files to tests, 3. Build and run and 4. Report
  • Calls cmake and git

What it does

Test Change is an agent skill from celeritas-project/celeritas. Build and run the unit tests covering changed Celeritas source files. Use after editing code under src/, app/, or test/ to verify the change, or when asked to run tests for specific files.

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 Testing & QA, covering Unit testing. It works with CUDA. The repository describes itself as: Celeritas is a new Monte Carlo transport code designed to accelerate scientific discovery in high energy physics by improving detector simulation throughput and energy efficiency…

When your agent uses it

  • Tasks that involve Unit testing

Example prompts

  • “/test-change”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Pick a build directory
  2. Map changed files to tests
  3. Build and run
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit f093ae2. 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

    Shell commands in SKILL.md call:

    • cmake
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Test Change loads about 640 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 281 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~640

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 281 words (~640 tokens).

“Verify a change by building and running only the affected tests.”

— opening of SKILL.md by celeritas-project, Custom licence
name
test-change

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/test-change of celeritas-project/celeritas.

Open the folder on GitHubat commit f093ae2

Compare with similar skills

Test Change 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.

Test Change compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Change this skillceleritas-project/celeritas105—~640Automated safety check: PassCustom licence
ONNX Runtime GPU Transformers Testsmicrosoft/onnxruntime22k—~2.9kAutomated safety check: PassMIT
Compilinggkeyllorg/gkeyll112—~759Automated safety check: PassMIT
Debug Failing GPUfacebookexperimental/triton201—~709Automated safety check: PassMIT
Ut Refactor Reviewintel/torch-xpu-ops115—~917Automated safety check: PassApache-2.0
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone

Similar skills

  • Official

    Runs the ONNX Runtime transformers Python tests against a GPU wheel and proves the cuDNN flash attention path was used rather than a silent fallback.

    22k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Compiling

    gkeyllorg/gkeyll

    How to compile Gkeyll libraries, executables, and specific unit or regression test targets on CPU or CUDA.

    112 GitHub stars~759 tokensUpdated today
    Testing & QAAuto-check passed
  • Debug Failing GPU

    facebookexperimental/triton

    Official

    Recover from GPU-busy / GPU-unavailable failures. An agent skill from facebookexperimental/triton.

    201 GitHub stars~709 tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Ut Refactor Review

    intel/torch-xpu-ops

    Official

    Review PyTorch upstream unit-test (UT) PRs that enable Intel GPU (XPU) on existing tests.

    115 GitHub stars~917 tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated yesterday
    Testing & QAAuto-check: notes

More from celeritas-project/celeritas

  • New Class

    celeritas-project/celeritas

    Scaffold new Celeritas source and test files with the required copyright header and register them in CMake.

    105 GitHub stars~496 tokensUpdated yesterday
    Auto-check passed
  • Debug Test

    celeritas-project/celeritas

    Update .vscode/launch.json to debug a specific CTest test by name.

    105 GitHub stars~199 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Test Change

What does Test Change do?

Build and run the unit tests covering changed Celeritas source files. Test Change is an agent skill from celeritas-project/celeritas. Build and run the unit tests covering changed Celeritas source files.

When should I use Test Change?

Test Change fits situations like: tasks that involve Unit testing.

How do I install Test Change in Claude Code?

Run `npx skills add celeritas-project/celeritas --skill test-change -a claude-code`. Or copy the skill folder (.claude/skills/test-change in celeritas-project/celeritas) into .claude/skills/test-change in your project. Claude Code loads it when a task matches its description.

How do I install Test Change in Codex?

Run `npx skills add celeritas-project/celeritas --skill test-change -a codex`. Or copy the skill folder (.claude/skills/test-change in celeritas-project/celeritas) into .agents/skills/test-change in your project. Codex loads it when a task matches its description.

Can I use Test Change 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 celeritas-project/celeritas --skill test-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-change, .gemini/skills/test-change, .github/skills/test-change and .opencode/skills/test-change in your project.

What does Test Change need to run?

Going by SKILL.md and its folder, Test Change needs the command-line tools its instructions call (cmake and git).

Does Test Change access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test Change 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 Test Change use?

Test Change has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Test Change use?

About 640 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 Test Change?

Skills that share tags, products or a category with Test Change: ONNX Runtime GPU Transformers Tests (microsoft/onnxruntime, 22k stars), Compiling (gkeyllorg/gkeyll, 112 stars), Debug Failing GPU (facebookexperimental/triton, 201 stars) and Ut Refactor Review (intel/torch-xpu-ops, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Change?

celeritas-project (a GitHub organization) maintains it in celeritas-project/celeritas, which has 105 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: celeritas-project/celeritas on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.