agentleFS
lgtm-hqlgtm-hq/ai-skills/skills/turbo-test/SKILL.md

turbo-test

Skill1 starsChanged 11 days agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the full build and test pipeline for turbo-themes.

    line 11
  2. Very specific:

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

    line 19
  3. Distinctive:

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

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ArgumentStagesUse when...
(none)All 5 stagesFull validation (default)
lintLint onlyQuick formatting/style check
buildBuild + examples:buildVerifying build works
unitUnit tests onlyRunning tests after a build
examplesexamples:build + examples:testValidating example projects
quickLint + build + unit testsFast 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.