How do I install the Turbo Test skill?

Run npx skillmds@latest add lgtm-hq/turbo-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Turbo Test safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Turbo Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Turbo Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Turbo Test?

lgtm-hq (@lgtm-hq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Turbo Test by lgtm-hq — Agent Skill

Name: Turbo Test
Author: lgtm-hq

File contents

Turbo-Themes Test Pipeline

Run the full build and test pipeline for turbo-themes. This project has a multi-stage pipeline where later stages depend on earlier outputs.

Do NOT use uv run lintro tst for this project — it does not cover the full turbo-themes pipeline (examples, E2E, site build).

Full Pipeline (default)

When /turbo-test is invoked with no arguments, run all stages in order:

# 1. Lint (fast fail — catches formatting/type issues early)
uv run lintro chk

# 2. Build core + packages
bun run build

# 3. Build example projects (depends on core build output)
bun run examples:build

# 4. Unit tests (~2000 tests across ~74 files, with coverage)
bun run test

# 5. Example E2E tests (~139 tests across example projects)
bun run examples:test

If any stage fails, stop and fix before continuing to the next stage.

Subcommands

Argument	Stages	Use when...
(none)	All 5 stages	Full validation (default)
`lint`	Lint only	Quick formatting/style check
`build`	Build + examples:build	Verifying build works
`unit`	Unit tests only	Running tests after a build
`examples`	examples:build + examples:test	Validating example projects
`quick`	Lint + build + unit tests	Fast check, skip examples

Optional E2E Stages

These are NOT part of the default pipeline. Run when explicitly needed:

# Smoke tests
bun run e2e:smoke

# Visual regression tests (snapshots generated on Linux CI only)
bun run e2e:visual

# Accessibility audits
bun run e2e:a11y

Note on visual regression: Snapshots are generated on Linux CI. Local failures on macOS are expected. Use the maintenance-generate-snapshots.yml workflow to regenerate snapshots after visual changes.

Rules

Lint before build — catches issues early without waiting for compilation.
Build before examples:build — examples depend on core package output.
Build before test — some tests depend on build artifacts (tokens.json, CSS).
Always include examples — example builds and tests are part of the standard pipeline, not optional extras. Do not skip them unless explicitly told to.

---name: turbo-testdescription: Run the full turbo-themes build and test pipeline. Use when asked to build, test, lint, or validate the turbo-themes project. Includes example projects by default.---# Turbo-Themes Test PipelineRun the full build and test pipeline for turbo-themes. This project has amulti-stage pipeline where later stages depend on earlier outputs.**Do NOT use `uv run lintro tst`** for this project — it does not cover thefull turbo-themes pipeline (examples, E2E, site build).## Full Pipeline (default)When `/turbo-test` is invoked with no arguments, run all stages in order:```bash# 1. Lint (fast fail — catches formatting/type issues early)uv run lintro chk# 2. Build core + packagesbun run build# 3. Build example projects (depends on core build output)bun run examples:build# 4. Unit tests (~2000 tests across ~74 files, with coverage)bun run test# 5. Example E2E tests (~139 tests across example projects)bun run examples:test```If any stage fails, stop and fix before continuing to the next stage.## Subcommands| Argument | Stages | Use when... || ---------- | ------------------------------ | ---------------------------- || _(none)_ | All 5 stages | Full validation (default) || `lint` | Lint only | Quick formatting/style check || `build` | Build + examples:build | Verifying build works || `unit` | Unit tests only | Running tests after a build || `examples` | examples:build + examples:test | Validating example projects || `quick` | Lint + build + unit tests | Fast check, skip examples |## Optional E2E StagesThese are NOT part of the default pipeline. Run when explicitly needed:```bash# Smoke testsbun run e2e:smoke# Visual regression tests (snapshots generated on Linux CI only)bun run e2e:visual# Accessibility auditsbun run e2e:a11y```**Note on visual regression:** Snapshots are generated on Linux CI. Localfailures on macOS are expected. Use the `maintenance-generate-snapshots.yml`workflow to regenerate snapshots after visual changes.## Rules- **Lint before build** — catches issues early without waiting for compilation.- **Build before examples:build** — examples depend on core package output.- **Build before test** — some tests depend on build artifacts (tokens.json, CSS).- **Always include examples** — example builds and tests are part of the standard pipeline, not optional extras. Do not skip them unless explicitly told to.

Frequently asked questions

Turbo Test