Test
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.From its SKILL.md
npx -y skills add lgtm-hq/ai-skills --skill testAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.0 KB, 663 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most unit integration skills give in 663 tokens
Counted across 149 of the 202 authors here whose files we hold, read 2026-09-06
- Structure tests as arrange, act, assertin 17 of 149
- Test behavior, not implementationin 16 of 149
- Mock all external dependenciesin 14 of 149
- Keep tests independentin 9 of 149
- Implement minimal code to passin 7 of 149
- Write a failing test firstin 7 of 149
- Fix or delete flaky tests immediatelyin 7 of 149
- Verify one behaviour per test functionin 7 of 149
- Name tests MethodName_StateUnderTest_ExpectedBehaviorin 6 of 149
- Separate arrange, act, and assert with blank linesin 6 of 149
- Target at least 80 percent core logic coveragein 6 of 149
- Create factory fixtures for test datain 6 of 149
Said here and by no other author read
- Run tests via lintro first
- Check package.json scripts for project-specific test commands
- Run the appropriate command for each detected framework
- Include a coverage report in every test run
- Review coverage reports after running
- Follow the test-shell skill for BATS guidance
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.