원클릭으로 Manus에서 모든 스킬 실행

vellum-test-selection

스타744

포크114

업데이트2026년 6월 17일 00:57

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

vellum-ai

vellum-ai/vellum-assistant

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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:

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

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

Common Commands

Assistant focused test:

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

Assistant test grep:

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

Assistant typecheck:

cd assistant && bunx tsc --noEmit

Gateway focused test:

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.

이 저장소의 다른 Skills

같은 저장소

messaging

vellum-ai/vellum-assistant

Read, search, send, and manage messages across Gmail, Outlook, Telegram, and other platforms

2026-06-23744

start-the-day

vellum-ai/vellum-assistant

An on-demand personal daily briefing — weather, headlines, the shape of your day, and one thing worth your attention — in a sharp executive-assistant voice. The general-purpose morning brief; richer work or admin digests compose it as their general layer.

2026-06-22744

vellum-memory-v3-migration

vellum-ai/vellum-assistant

One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.

2026-06-22744

workflows

vellum-ai/vellum-assistant

Delegate a big or high-stakes job to a fleet of parallel subagents, orchestrated deterministically; runs unattended and reports back

2026-06-22744

contacts

vellum-ai/vellum-assistant

Manage contacts, communication channels, access control, and invite links

2026-06-22744

app-builder

vellum-ai/vellum-assistant

Build 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).

2026-06-22744

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

Setup

Before any Bun command:

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

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

Common Commands

Assistant focused test:

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

Assistant test grep:

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

Assistant typecheck:

cd assistant && bunx tsc --noEmit

Gateway focused test:

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.