running-vitest-safely
Use this skill when running Vitest tests to ensure safe execution. Applies when running tests, executing test suites, or invoking pnpm test, npm test, or vitest commands. Prevents hung processes through timeouts, manages watch mode, and ensures proper cleanup. Essential for automated test runs to avoid runaway processes consuming CPU for hours or days.
What this skill does
# Running Vitest Tests Safely
This skill ensures Vitest tests run safely without creating hung processes that consume system resources indefinitely.
## Pre-Flight Check
**ALWAYS check for existing Vitest processes before starting new tests:**
```bash
pgrep -f "vitest" && echo "WARNING: Existing vitest processes found"
```
If processes exist, either:
1. Wait for them to complete
2. Kill them if they appear stuck: `pkill -f "vitest"`
## Required Flags for Safe Execution
### 1. Disable Watch Mode (Critical)
Always use `--run` to ensure tests exit after completion:
```bash
# Correct - will exit after tests complete
pnpm vitest --run
# NEVER use in automated contexts (will hang indefinitely)
pnpm vitest # Bad - defaults to watch mode
pnpm vitest --watch # Bad - explicit watch mode
```
### 2. Set Timeouts (Critical)
Always set timeouts to prevent infinite hangs:
```bash
# Set per-test timeout (default: 5000ms, recommended: 30000ms for safety)
pnpm vitest --run --testTimeout=30000
# Set hook timeout for beforeAll/afterAll
pnpm vitest --run --hookTimeout=30000
```
### 3. Fail Fast with --bail
Stop on first failure to avoid wasting resources:
```bash
# Stop after first test failure
pnpm vitest --run --bail
# Or stop after N failures
pnpm vitest --run --bail=3
```
## Recommended Command Pattern
Combine all safety flags:
```bash
pnpm vitest --run --testTimeout=30000 --hookTimeout=30000 --bail
```
For running specific test files:
```bash
pnpm vitest --run --testTimeout=30000 path/to/test.test.ts
```
## Process Isolation
For better stability, consider using forks pool:
```bash
pnpm vitest --run --pool=forks --testTimeout=30000
```
## Post-Run Verification
After tests complete, verify no processes remain:
```bash
pgrep -f "vitest" || echo "Clean: No vitest processes running"
```
## Handling Stuck Processes
If Vitest processes are stuck:
```bash
# Graceful termination
pkill -f "vitest"
# Force kill if needed (wait a few seconds first)
pkill -9 -f "vitest"
# Find and kill specific PIDs
ps aux | grep vitest | grep -v grep
kill <PID>
```
## Configuration File Alternative
For projects using vitest.config.ts, add default timeouts:
```typescript
export default defineConfig({
test: {
testTimeout: 30000,
hookTimeout: 30000,
// Disable watch mode by default
watch: false,
},
})
```
## Summary Checklist
Before running tests, ensure:
- [ ] No existing vitest processes running (`pgrep -f vitest`)
- [ ] Using `--run` flag (no watch mode)
- [ ] Timeout set (`--testTimeout=30000`)
- [ ] Consider `--bail` for early failure detection
## Quick Reference
| Flag | Purpose | Recommended Value |
|------|---------|-------------------|
| `--run` | Disable watch mode | Always use |
| `--testTimeout` | Per-test timeout | 30000 (30s) |
| `--hookTimeout` | Hook timeout | 30000 (30s) |
| `--bail` | Stop on failure | Use for CI |
| `--pool=forks` | Process isolation | Optional |
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.