test
Skill25 starsChanged 19 days agoApache-2.0View on GitHub
Run the relevant tests for what changed — detects whether to run C# unit tests, specific test projects, integration tests, or JS/TS tests based on changed files. Use when the user asks to run tests, verify changes, or check if something is broken.
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 144 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Use this decision table based on which directories have changed files:
- Very specific: line 38
If files span more than two source areas, prefer ./build.sh unit-test to run all unit tests at once.
- Very specific: line 49
When in doubt, ./build.sh unit-test is the safe default (completes in under a minute)
“Common” is measured: kept by at least 6 in 10 of the 144 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
Test Skill
Runs the right tests for what changed — fast feedback without running everything.
Steps
1. Detect changed files
git diff --name-only HEADOr, if checking staged changes:
git diff --name-only --staged2. Pick the right test command
Use this decision table based on which directories have changed files:
| Changed path | Test command |
src/Elastic.Documentation.Site/ | cd src/Elastic.Documentation.Site && npm run test; shared views or layout CSS also npm run visual:seed once, then npm run visual:check |
src/Elastic.Markdown/ | dotnet test tests/Elastic.Markdown.Tests/ |
src/Elastic.Documentation.Configuration/ | dotnet test tests/Elastic.Documentation.Configuration.Tests/ |
src/Elastic.Documentation.Navigation/ or Navigation.Tests/ | dotnet test tests/Navigation.Tests/ |
src/Elastic.ApiExplorer/ | dotnet test tests/Elastic.ApiExplorer.Tests/ |
tests-integration/ | ./build.sh integrate |
src/tooling/docs-builder/ | ./build.sh unit-test |
| Multiple areas or uncertain | ./build.sh unit-test |
If files span more than two source areas, prefer ./build.sh unit-test to run all unit tests at once.
3. Run and report
- Show the command being run
- On pass: summarize pass count, confirm all green
- On fail: show the specific failing test(s), the error message, and suggest a fix approach based on the failure
Notes
- Integration tests (
./build.sh integrate) require cloned repos and take significantly longer — only run when integration test files changed or the user explicitly asks - When in doubt,
./build.sh unit-testis the safe default (completes in under a minute) - TypeScript type checking (not tests) is
npm run compile:checkfromsrc/Elastic.Documentation.Site/
Other versions169 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 169
- react/react★ 252ksame name
- facebook/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 11ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.1ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
159 more not listed
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.
Used alongsideProjects with it also use agent-context-isolation, agentica-infrastructure and 10 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.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
parcadeiSkillagentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- src/Elastic.ApiExplorer/AGENTS.mdAGENTS.md
- src/Elastic.Documentation.Site/AGENTS.mdAGENTS.md
- src/Elastic.Markdown/AGENTS.mdAGENTS.md
- src/services/search/Elastic.Documentation.Search.Contract/AGENTS.mdAGENTS.md
- commitSkill
- feature-flagSkill
- issueSkill
- lintSkill
- mcp-searchSkill
- prSkill
- style-reviewSkill
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.

