Vellum Test Selection

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/.cursor/skills/vellum-test-selectionThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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.

---
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/web`, or `clients/macos`.

## 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/persistence/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.

Excerpt, first 2,299 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/vellum-ai/vellum-assistant
git -C vellum-assistant checkout 19bc86343b63

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 19bc86343b63

Questions about Vellum Test Selection

• github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/v — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology