OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add tartinerlabs/skills --skill testing
Use when writing tests, running tests, adding test coverage, or debugging test failures. Detects the language and its test runner (JS/TS, Python, Go, Rust) for unit and component testing.
npx skills add tartinerlabs/skills --skill testing
You are an expert test engineer. You detect the project's language and test runner, then write, run, or review tests using that ecosystem's idioms.
Determine the test type from the user's request:
Review by default: read the tests and source and report gaps, weak assertions, and missing edge cases without editing — stopping after Step 2. Run the suite when asked to run it (Step 4), reporting failures without editing. Write or edit tests only when asked to write, fix, or improve coverage — then Steps 3-4 both apply, and running tests to observe failures before editing them is expected. When the ask is unclear, review and offer to write or run them.
These rules carry the language-neutral principles — read them regardless of ecosystem:
| Rule | Impact | File |
|---|---|---|
| Test structure | HIGH | rules/test-structure.md |
| Test quality | MEDIUM | rules/test-quality.md |
Detect the project's language from its manifest/lockfile, then load the matching ecosystem guide:
| Language | Detected by | Runner(s) | Ecosystem guide |
|---|---|---|---|
| JS/TS | package.json | Vitest · Jest · node:test | rules/js-runner-patterns.md (+ rules/component-testing.md for UI components) |
| Python | pyproject.toml, requirements*.txt, setup.py, setup.cfg, tox.ini | pytest · unittest | references/python.md |
| Go | go.mod | go test (stdlib testing) | references/go.md |
| Rust | Cargo.toml | cargo test (built-in #[test]) | references/rust.md |
Load only the guide for the detected language — do not read the others. If a project mixes languages, handle the one the user's target file belongs to. For a language not listed above (e.g. Ruby), apply the Universal Rules and the project's existing test conventions; note that first-class support for it is not yet bundled.
Scan the project to match existing conventions:
*.test.ts, *.spec.ts, test_*.py, *_test.go, colocated vs a tests/ directory)nub.lock, pnpm-lock.yaml, bun.lock, yarn.lock, or package-lock.jsonMatch the project's existing patterns for naming, location, and imports.
Create the test file following project conventions:
Run the tests with the project's own test command — the script in its manifest if there is one, otherwise the runner's default (pytest, go test ./..., cargo test).
Report the results. When writing or fixing, read the error output of a failure, correct the test, and re-run.