vellum-test-selection

Selects focused test, typecheck, and lint commands for Vellum Assistant code changes.

1.2k|166|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/vellum-ai/vellum-assistant --skill vellum-test-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vellum-test-selection
Source: https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-test-selection
Command: npx skills add https://github.com/vellum-ai/vellum-assistant --skill vellum-test-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running the full Bun test suite in the Vellum Assistant repository is slow and can hang or time out, making it impractical to verify changes before commits and pull requests. This Skill guides the selection of focused verification commands based on which files were edited.

Core Features & Use Cases

  • Focused Test Selection: Maps changed files to their owning package (assistant, gateway, cli, clients/web, clients/macos) and runs only the matching test files with Bun.
  • Risk-Based Typechecking: Adds bunx tsc --noEmit when edits touch exported types, route shapes, daemon/client protocols, migrations, or provider abstractions.
  • Migration Test Triggers: Runs migration tests when persistence, workspace migration, or database schema modules change.
  • Use Case: After editing a route handler in the gateway package, use this Skill to run the nearby gateway test file plus a package typecheck instead of the entire suite, then report which checks were intentionally skipped.

Quick Start

Ask the assistant to choose and run the right verification commands for the files changed in this branch before opening a pull request.

Frequently Asked Questions about vellum-test-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run only specific tests with Bun instead of the full suite?

Run a single test file with `bun test src/path/to/file.test.ts` from the owning package directory, or narrow further with `--grep "case name"`. This avoids the full suite, which can hang or time out in large repositories.

How do I decide which tests to run after editing code?

Group changed files by package, then run the test file matching each edited implementation file. For route, protocol, migration, or schema changes, also run nearby tests plus a package typecheck to catch cross-module breakage.

When should I add a TypeScript typecheck to test runs?

Add `bunx tsc --noEmit` when edits touch exported types, route request/response shapes, daemon/client protocols, migrations, package boundary imports, provider abstractions, or feature flag registry code.

Why does running the full Bun test suite hang or time out?

Large monorepo suites execute thousands of tests across packages, some involving long-running integration or migration scenarios. Scoping tests to changed files keeps verification fast and avoids timeouts.

What tests should run for database migration changes?

Run migration tests whenever edits touch persistence migrations, workspace migrations, persisted workspace files, or database schema modules, since these affect stored data compatibility across versions.