skills.rest
Logarn
LogarnCOMMUNITY
Explore all skills by this author →
GitHub

vellum-test-selection

Selects focused test, typecheck, and lint commands for Bun monorepo changes.

1|Updated Mar 30, 2026
Search Tags:#verification#monorepo#pre-commit#bun#test selection#typecheck#focused testing
One-click install
npx skills add https://github.com/Logarn/Worklin-ai --skill vellum-test-selection-logarn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vellum-test-selection
Source: https://github.com/Logarn/Worklin-ai/tree/main/.cursor/skills/vellum-test-selection
Command: npx skills add https://github.com/Logarn/Worklin-ai --skill vellum-test-selection-logarn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an unscoped full test suite in a large Bun monorepo can hang or time out, wasting developer time before commits and pull requests. This Skill maps changed files to the right focused verification commands so only relevant tests, typechecks, and smoke checks run. ## Core Features & Use Cases - Focused Test Selection: Groups changed files by package and runs only the matching test files or grep-scoped test cases with bun test. - Risk-Based Typechecking: Adds bunx tsc --noEmit when edits touch shared TypeScript contracts, route shapes, protocols, migrations, or provider abstractions. - Migration Coverage: Triggers migration tests when changes affect memory or workspace migration directories and database schema modules. - Use Case: After editing a gateway route handler and a shared contract type, the Skill directs running the gateway test file plus typechecks for each consumer package instead of the full suite. ## Quick Start Ask the assistant to choose which tests and typechecks to run for the files changed in your current branch before committing.

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 in a Bun monorepo?▼

Run bun test with the path to the specific test file from the owning package directory, such as cd assistant && bun test src/path/to/file.test.ts. Use --grep with a case name to narrow execution to a single test within that file.

How to choose which tests to run after editing code?▼

Group changed files by package, run the matching test file for direct implementation and test pairs, and add nearby tests plus a package typecheck for route, protocol, migration, or schema changes. Shared contract edits require tests for each consumer package.

When should I add a TypeScript typecheck to test runs?▼

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

Why does running the full bun test suite hang in large repositories?▼

Large monorepo suites contain many integration and long-running tests that can exceed time limits or block on resources. Running focused, package-scoped test files avoids this and gives faster feedback on the actual changes.

What tests are needed for database migration changes?▼

Migration changes under memory or workspace migration directories, persisted workspace files, or database schema modules require dedicated migration tests in addition to the focused unit tests for the edited files.

Related Skills

Explore More Software Engineering Skills→
thoreinsteinthoreinstein
5

commit

Analyze git diffs to plan atomic commits with grouped files and messages.

Community
Basic
4armsxlr84armsxlr8

verify-local

Execute build, test, and lint commands to verify local code integrity.

Community
Intermediate
eygrabereygraber
1

check

Run formatting, detekt, lint, and unit tests on Android and Kotlin projects.

Community
Intermediate
SavigeSystemZSavigeSystemZ

debug-playbook

Reproduces, isolates, and resolves failures in build, test, run-time, packaging, or install workflows.

Official
Advanced