Agent skill

Test Changed

by stellar in stellar/laboratory

Run e2e and unit tests related to files changed on the current branch.

Apache-2.0Auto-check passedTesting & QA

Install Test Changed

skills CLI
$ npx skills add stellar/laboratory --skill test-changed -a claude-code

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

GitHub CLI
$ gh skill install stellar/laboratory test-changed --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/stellar/laboratory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/test-changed .claude/skills/test-changed && 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-changed
GitHub stars
112
Token cost
~836 tokens
SKILL.md length
280 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run e2e and unit tests related to files changed on the current branch.

  • Works in 6 steps: Kill any stale dev server on port 3000… → Find changed files relative to main → Map source changes to test files. Use… → …
  • Tasks that involve Unit testing
  • Calls pnpm, git and npx
  • Tasks that involve End-to-end testing

What it does

Test Changed is an agent skill from stellar/laboratory. Run e2e and unit tests related to files changed on the current branch. Use after making code changes to verify nothing is broken.

Its SKILL.md is about 840 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 and End-to-end testing. It works with Playwright. The repository describes itself as: A set of tools that enables developers to try out and learn about the Stellar network. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Unit testing
  • Tasks that involve End-to-end testing

Example prompts

  • “/test-changed”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Kill any stale dev server on port 3000 before running e2e tests. Playwright's reuseExistingServer will pick up a server from a different…
  2. Find changed files relative to main
  3. Map source changes to test files. Use these rules
  4. If XDR encoding or transaction building logic changed (e.g. ClassicTransactionXdr.tsx, SorobanTransactionXdr.tsx, src/helpers/xdr/)…
  5. Run the identified tests
  6. Report results. Show pass/fail counts and list any failures with their error messages. For failures, read the relevant test code and…

What it can do on your machine

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

    • pnpm
    • git
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, git and npx, 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 Changed loads about 836 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 280 words of instructions outside code blocks.

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

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 stellar/laboratory at commit b4b6465, republished under its Apache-2.0 licence (© stellar). 280 words, ~836 tokens.

Download SKILL.mdSave it as .claude/skills/test-changed/SKILL.md (or your agent's skills folder).
name
test-changed
description
Run e2e and unit tests related to files changed on the current branch. Use after making code changes to verify nothing is broken.

Run Tests for Changed Files

Run e2e and unit tests that are relevant to the files changed on the current branch.

Test Configuration
  • Unit (Jest): Config in jest.config.js, path aliases via moduleNameMapper
  • E2E (Playwright): Config in playwright.config.ts, Chromium only, 20s timeout per test, 2 retries, 2 workers
  • E2E dev server: Playwright starts pnpm dev automatically, but reuseExistingServer: true in non-CI — a stale server from another branch will cause false failures
Steps
  1. Kill any stale dev server on port 3000 before running e2e tests. Playwright's reuseExistingServer will pick up a server from a different branch otherwise, causing false failures (especially in worktrees):

    bash
    lsof -ti:3000 | xargs kill -9 2>/dev/null; true
  2. Find changed files relative to main:

    bash
    git diff --name-only main...HEAD
    git diff --name-only          # unstaged
    git diff --name-only --cached # staged
  3. Map source changes to test files. Use these rules:

    • src/app/(sidebar)/transaction/build/** -> tests/e2e/buildTransaction.test.ts, tests/e2e/savedTransactions.test.ts, tests/e2e/urlParams.test.ts
    • src/app/(sidebar)/transaction/sign/** -> tests/e2e/signTransactionPage.test.ts
    • src/app/(sidebar)/transaction/submit/** -> tests/e2e/submitTransactionPage.test.ts
    • src/app/(sidebar)/transaction/simulate/** -> tests/e2e/simulateTransactionPage.test.ts
    • src/app/(sidebar)/transaction/fee-bump/** -> tests/e2e/feeBumpTransactionPage.test.ts
    • src/app/(sidebar)/account/fund/** or src/app/(sidebar)/account/create/** -> tests/e2e/fundAccountPage.test.ts, tests/e2e/createAccountPage.test.ts
    • src/app/(sidebar)/xdr/** -> tests/e2e/viewXdrToJsonPage.test.ts, tests/e2e/jsonToXdrPage.test.ts
    • src/app/(sidebar)/endpoints/** -> tests/e2e/endpointsPage*.test.ts
    • src/app/(sidebar)/smart-contracts/** -> tests/e2e/contractExplorer*.test.ts
    • Shared code — run ALL e2e tests: src/components/**, src/helpers/**, src/hooks/**, src/store/**, src/constants/**, src/types/**, src/validate/**, src/styles/**, src/middleware.ts
    • tests/e2e/mock/** -> run ALL e2e tests that import from mock/
    • tests/e2e/*.test.ts changed directly -> run those tests
    • tests/unit/** changed -> run unit tests
    • If source files under src/helpers/ or src/validate/ changed, also check tests/unit/ for matching unit tests
  4. If XDR encoding or transaction building logic changed (e.g. ClassicTransactionXdr.tsx, SorobanTransactionXdr.tsx, src/helpers/xdr/), hardcoded hash/XDR values in tests may need updating. Flag this to the user before running tests.

  5. Run the identified tests:

    • E2E: npx playwright test <file1> <file2> ... --retries=0 --reporter=list
    • Unit: pnpm test:unit <file>
    • If no specific tests identified, run the full suite: pnpm test:e2e and pnpm test:unit
  6. Report results. Show pass/fail counts and list any failures with their error messages. For failures, read the relevant test code and source code to suggest fixes.

© stellar, Apache-2.0. 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 .claude/skills/test-changed of stellar/laboratory.

Open the folder on GitHubat commit b4b6465

Compare with similar skills

Test Changed 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 Changed compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Changed this skillstellar/laboratory112—~836Automated safety check: PassApache-2.0
VerifyGnathonic/mokuro-reader209—~724Automated safety check: PassGPL-3.0
Pierre Testing and Verification Guidepierrecomputer/pierre6.2k—~608Automated safety check: PassApache-2.0
Svelte Testingspences10/sveltest113—~579Automated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Verify

    Gnathonic/mokuro-reader

    Verify reader features end-to-end by importing a synthetic volume through the real upload modal and driving the reader with Playwright.

    209 GitHub stars~724 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Chooses the right verification step after a code change in Pierre's monorepo: format and lint, a typecheck, Bun unit tests, snapshots, or Playwright E2E.

    6.2k GitHub stars~608 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Svelte Testing

    spences10/sveltest

    Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

    113 GitHub stars~579 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.2k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

More from stellar/laboratory

  • Component Guide

    stellar/laboratory

    Guide for building React components using @stellar/design-system and project SCSS conventions.

    112 GitHub stars~999 tokensUpdated 4 days ago
    Auto-check passed
  • Correct mental models for React re-renders and memoization. An agent skill from stellar/laboratory.

    112 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed
  • Zustand Store Patterns

    stellar/laboratory

    Reference for the two Zustand store patterns in Stellar Lab — main store (querystring) and transaction flow store (sessionStorage).

    112 GitHub stars~1.4k tokensUpdated 4 days ago
    Auto-check passed
  • Commit Progress

    stellar/laboratory

    Commit a logical unit of work with a descriptive message. An agent skill from stellar/laboratory.

    112 GitHub stars~774 tokensUpdated 4 days ago
    Auto-check: notes
  • Figma To Code

    stellar/laboratory

    Bridge Figma MCP output to Stellar Lab code conventions. An agent skill from stellar/laboratory.

    112 GitHub stars~520 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Test Changed

What does Test Changed do?

Run e2e and unit tests related to files changed on the current branch. Test Changed is an agent skill from stellar/laboratory. Run e2e and unit tests related to files changed on the current branch.

When should I use Test Changed?

Test Changed fits situations like: tasks that involve Unit testing; tasks that involve End-to-end testing.

How do I install Test Changed in Claude Code?

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

How do I install Test Changed in Codex?

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

Can I use Test Changed 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 stellar/laboratory --skill test-changed -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-changed, .gemini/skills/test-changed, .github/skills/test-changed and .opencode/skills/test-changed in your project.

What does Test Changed need to run?

Going by SKILL.md and its folder, Test Changed needs the command-line tools its instructions call (pnpm, git and npx). Our summary lists: Node.js.

Does Test Changed access the network?

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

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

Test Changed is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Changed use?

About 836 tokens (SKILL.md is roughly 3.3k 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 Changed?

Skills that share tags, products or a category with Test Changed: Verify (Gnathonic/mokuro-reader, 209 stars), Pierre Testing and Verification Guide (pierrecomputer/pierre, 6.2k stars), Svelte Testing (spences10/sveltest, 113 stars) and Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Changed?

stellar (a GitHub organization) maintains it in stellar/laboratory, which has 112 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 3, 2026.

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