vellum-test-selection

$npx mdskill add vellum-ai/vellum-assistant/vellum-test-selection

Select focused verification commands for Vellum Assistant changes

  • Identifies and runs relevant tests based on changed files in the repository.
  • Depends on the `PATH` environment variable to locate test scripts.
  • Decides which tests to run by grouping changed files, considering their package ownership and impact.
  • Delivers results directly through command execution for immediate feedback.

SKILL.md

.github/skills/vellum-test-selectionView on GitHub ↗
---
name: vellum-test-selection
description: Select focused verification commands for Vellum Assistant changes. Use when deciding what tests, typechecks, lints, or smoke checks to run after editing this repository, especially before commits and pull requests.
---

# Vellum Test Selection

## Core Rule

Never run unscoped `bun test` in this repository. The full suite is large and can hang or time out. Choose focused tests based on changed files, then add typechecking when the change affects shared contracts or cross-package behavior.

## Setup

Before any Bun command:

```bash
export PATH="$HOME/.bun/bin:$PATH"
```

Run commands from the package directory that owns the changed files, usually `assistant`, `gateway`, `cli`, `clients/macos`, or `clients/tauri`.

## Selection Workflow

1. List changed files and group them by package.
2. For direct implementation/test pairs, run the matching test file.
3. For route, protocol, migration, IPC, provider, or schema changes, run nearby tests plus a package typecheck.
4. For shared TypeScript contracts, run tests for each consumer package that imports the contract.
5. For Swift or macOS client changes, prefer the existing platform-specific test command if one is already used in nearby docs or terminal history.
6. If a command is expected to be long-running, state that before running it.

## Common Commands

Assistant focused test:

```bash
cd assistant && bun test src/path/to/file.test.ts
```

Assistant test grep:

```bash
cd assistant && bun test src/path/to/file.test.ts --grep "case name"
```

Assistant typecheck:

```bash
cd assistant && bunx tsc --noEmit
```

Gateway focused test:

```bash
cd gateway && bun test src/path/to/file.test.ts
```

## Risk-Based Additions

Add typecheck when edits touch:

- exported TypeScript types or schemas
- route request/response shapes
- daemon/client protocols
- migrations and registry wiring
- package boundary imports
- provider abstractions
- feature flag registry or resolver code

Add migration tests when edits touch:

- `assistant/src/memory/migrations/`
- `assistant/src/workspace/migrations/`
- persisted workspace files
- database schema modules

## Reporting

When proposing or running verification, explain why each command is selected and note anything intentionally skipped.

More from vellum-ai/vellum-assistant

SkillDescription
acpSpawn external coding agents via the Agent Client Protocol (ACP)
amazonShop on Amazon and Amazon Fresh through your browser
api-mappingRecord and analyze API surfaces of web services
app-builderBuild and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).
app-controlDrive a specific named macOS app via raw input bypassing the Accessibility tree
assistant-migrationMigrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
chatgpt-importImport conversation history from ChatGPT into Vellum
cli-discoverDiscover which CLI tools are installed, their versions, and authentication status
contactsManage contacts, communication channels, access control, and invite links
conversation-launcherOffer the user several spin-off conversations as clickable buttons on a single persistent card. Each click spawns a fresh seeded conversation in the sidebar; the user keeps their place in the current conversation. Use when you want to branch into N focused threads (research directions, draft choices, pending replies, triage of N items) without losing the current context. Not for single-destination pivots — just reply inline.