test
Skill1 starsChanged 10 days agoMITView on GitHub
Run tests with coverage reporting. Auto-detects test frameworks (Vitest, Playwright, RSpec, pytest, Jest, BATS, etc.) and runs appropriate test commands. Use when asked to run tests, check coverage, or validate code.
179 other projects use a version of this.
Adopted by
Most recently taken up by
- tyrantpiper/travel-pwatheir own version, first seen Nov 8, 2026
- phuthuycoding/kanban-flowtheir own version, first seen Nov 8, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 8, 2026
- PMDevSolutions/Flaviantheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
Used with
Projects 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
- parcadeiSkill
agentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions179 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 179
- react/react★ 252ksame name
- facebook/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 10ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
169 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.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- stand-tsSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
6
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 8
Run tests with coverage reporting.
- Distinctive: line 17
When lintro is unavailable or you need to run specific test types, detect frameworks by checking for:
- Very specific: line 33
Check package.json scripts for project-specific test commands
- Distinctive: line 35
Run tests with coverage enabled and include a coverage report in every test run (this skill owns the coverage policy)
- Distinctive: line 40
When asked to run tests:
- Distinctive: line 44
Check for config files to detect frameworks
- Very specific: line 45
Check package.json for test scripts
- Distinctive: line 46
Run the appropriate command for each framework
“Common” is measured: kept by at least 6 in 10 of the 154 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
Run tests with coverage reporting. This skill auto-detects test frameworks in the project.
Primary Command
uv run lintro tst- Run tests via lintro (handles multiple frameworks)
Framework Detection
When lintro is unavailable or you need to run specific test types, detect frameworks by checking for:
| Framework | Config Files | Test Patterns | Run Command |
| Vitest | vitest.config.ts | *.test.ts, *.spec.ts | bun test or bunx vitest |
| Jest | jest.config.js | *.test.js, *.spec.js | bun test or bunx jest |
| Playwright | playwright.config.ts | e2e/*.spec.ts | bun run e2e or bunx playwright test |
| RSpec | .rspec, Gemfile | spec/*_spec.rb | bundle exec rspec |
| pytest | pytest.ini, pyproject.toml | test_*.py, *_test.py | uv run pytest |
| BATS | tests/bats/, tests/helpers/ | *.bats | bats --recursive tests/bats/ |
| Go | go.mod | *_test.go | go test ./... |
| Rust | Cargo.toml | #[test] functions | cargo test |
Rules
- Check
package.jsonscripts for project-specific test commands - For shell tests, follow the
test-shellskill for detailed BATS guidance - Run tests with coverage enabled and include a coverage report in every test run (this skill owns the coverage policy)
Usage
When asked to run tests:
- Try lintro first:
uv run lintro tst - If lintro unavailable or specific tests needed:
- Check for config files to detect frameworks
- Check
package.jsonfor test scripts - Run the appropriate command for each framework
- Review coverage reports
- Ensure test coverage for new/modified code
Writing Tests
For how to write tests, delegate to the appropriate skill:
| Stack / tool | Skill |
| Python (pytest) | stand-py |
| TypeScript/JavaScript (Vitest/Jest) | stand-ts |
Rust (cargo test) | stand-rust |
| Shell (BATS) | test-shell |
| Playwright E2E | test-ui |
| Playwright API | test-api |
For other frameworks (RSpec, Go), follow project conventions and the patterns detected above.
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.