Skills vitest-testing

📦

vitest-testing

Name: vitest-testing
Author: AdamManuel-dev

Content revision r1 High Risk 🌐 Network access📁 Filesystem access⚙️ External commands🔑 Env variables⚡ Contains scripts

Build Reliable Vitest Test Suites

Writing useful tests is hard when examples are scattered across unit, integration, component, and E2E workflows. This skill gives Claude, Codex, and Claude Code structured Vitest guidance for choosing patterns, writing tests, and improving testability.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "vitest-testing" from https://skillstore.io/skills/adammanuel-dev-vitest-testing.md and its manifest at https://skillstore.io/api/skills/adammanuel-dev-vitest-testing/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/adammanuel-dev-vitest-testing.md Signed manifest GET /api/skills/adammanuel-dev-vitest-testing/manifest Signed lockfile GET /api/skills/adammanuel-dev-vitest-testing/lockfile

Test it

Using "vitest-testing". Help me test a service that validates users and writes to a database.

Expected outcome:

A recommendation to unit test validation with mocks and integration test the repository boundary.
A small test plan organized by behavior, failure paths, and database cleanup needs.
Notes about avoiding production database access and keeping fixtures isolated.

Using "vitest-testing". My React component test passes locally but fails in CI.

Expected outcome:

A checklist for async rendering, user events, timers, cleanup, and environment differences.
Suggested Vitest and Testing Library patterns for stable assertions.
A warning to avoid sleeps and assert visible behavior instead.

Using "vitest-testing". Convert these Jest mocks to Vitest.

Expected outcome:

A mapping from Jest mock APIs to Vitest equivalents.
Guidance on hoisting, import timing, module factories, and restoring mocks.
Migration risks to verify with the real test runner.

Security Audit

High Risk

v10 • 7/9/2026 Open versioned report

Most static matches are false positives caused by testing documentation, Markdown links, JavaScript template literals, and normal Vitest examples. I confirmed a smaller set of risks around user-local hidden Claude skill paths, environment mutation or state capture, API-key configuration, shell guidance, and destructive database cleanup examples that should be clarified before publication. Static review was capped at 400/442 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

Files scanned

14,285

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (7)

High

patterns/integration-testing.md:222

Environment file access

const testApiKey = process.env.STRIPE_TEST_KEY

The example reads a payment provider test API key from the environment. It is legitimate for integration tests, but still handles secret-like configuration and should be kept for review.

High

patterns/test-data.md:659

Environment file access

process.env[envKey] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

High

patterns/test-data.md:696

Environment file access

manager.saveState('env.NODE_ENV', process.env.NODE_ENV)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

High

patterns/test-data.md:697

Environment file access

manager.saveState('env.API_URL', process.env.API_URL)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

High

patterns/test-data.md:705

Environment file access

process.env[key.substring(4)] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/integration-testing.md:56

SQLite database file

await this.db.raw('TRUNCATE TABLE users CASCADE')

The example contains destructive database cleanup commands. It is intended for tests, but is dangerous if copied against a non-test database.

Medium

patterns/integration-testing.md:57

SQLite database file

await this.db.raw('TRUNCATE TABLE orders CASCADE')

The example contains destructive database cleanup commands. It is intended for tests, but is dangerous if copied against a non-test database.

Capability review items (38)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High

patterns/e2e-testing.md:54

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && \

The example directs access to user-local hidden Claude skill paths, including command execution from ~/.claude or an absolute home directory. This is risky for marketplace distribution because it can train agents to touch private local skill directories.

High

patterns/e2e-testing.md:63

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

High

patterns/e2e-testing.md:126

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

High

patterns/e2e-testing.md:144

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

High

patterns/e2e-testing.md:621

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-login.js

High

patterns/e2e-testing.md:689

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-debug-selectors.js

High

patterns/e2e-testing.md:744

Hidden file in home directory

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-registration.js

High

STATUS.md:209

Hidden file in home directory

cd ~/.claude/skills/playwright-skill

Medium

patterns/e2e-testing.md:54

Hidden file access

cd ~/.claude/skills/playwright-skill && \

Medium

patterns/e2e-testing.md:63

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:126

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:144

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:579

Hidden file access

const helpers = require('/Users/adammanuel/.claude/skills/playwright-skill/lib/helpers');

Medium

patterns/e2e-testing.md:621

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-login.js

Medium

patterns/e2e-testing.md:689

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-debug-selectors.js

Medium

patterns/e2e-testing.md:699

Hidden file access

const helpers = require('/Users/adammanuel/.claude/skills/playwright-skill/lib/helpers');

Medium

patterns/e2e-testing.md:744

Hidden file access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-registration.js

Medium

STATUS.md:187

Hidden file access

open /Users/adammanuel/.claude/skills/vitest-testing/README.md

Medium

STATUS.md:190

Hidden file access

open /Users/adammanuel/.claude/skills/vitest-testing/quick-reference/cheatsheet.md

Medium

STATUS.md:193

Hidden file access

open /Users/adammanuel/.claude/skills/vitest-testing/index.md

Medium

STATUS.md:209

Hidden file access

cd ~/.claude/skills/playwright-skill

Medium

patterns/e2e-testing.md:63

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:126

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:144

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-checkout.js

Medium

patterns/e2e-testing.md:621

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-login.js

Medium

patterns/e2e-testing.md:689

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-debug-selectors.js

Medium

patterns/e2e-testing.md:744

Temp directory access

cd ~/.claude/skills/playwright-skill && node run.js /tmp/playwright-test-registration.js

Medium

quick-reference/jest-to-vitest.md:448

Unix shell invocation

#!/bin/bash

The finding indicates a shell invocation in documentation. It may be legitimate migration guidance, but shell commands should remain explicit and reviewed before marketplace publication.

Medium

patterns/test-data.md:659

Environment variable access (bracket notation)

process.env[envKey] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/test-data.md:705

Environment variable access (bracket notation)

process.env[key.substring(4)] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/integration-testing.md:222

Environment variable access (dot notation)

const testApiKey = process.env.STRIPE_TEST_KEY

The example reads a payment provider test API key from the environment. It is legitimate for integration tests, but still handles secret-like configuration and should be kept for review.

Medium

patterns/test-data.md:696

Environment variable access (dot notation)

manager.saveState('env.NODE_ENV', process.env.NODE_ENV)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/test-data.md:697

Environment variable access (dot notation)

manager.saveState('env.API_URL', process.env.API_URL)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/integration-testing.md:222

Environment variable object

const testApiKey = process.env.STRIPE_TEST_KEY

The example reads a payment provider test API key from the environment. It is legitimate for integration tests, but still handles secret-like configuration and should be kept for review.

Medium

patterns/test-data.md:659

Environment variable object

process.env[envKey] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/test-data.md:696

Environment variable object

manager.saveState('env.NODE_ENV', process.env.NODE_ENV)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/test-data.md:697

Environment variable object

manager.saveState('env.API_URL', process.env.API_URL)

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Medium

patterns/test-data.md:705

Environment variable object

process.env[key.substring(4)] = value

The snippet mutates or stores environment-variable state in test examples. It appears test-scoped, but can leak or persist sensitive configuration if copied without isolation.

Risk Factors

🌐 Network access (46)

📁 Filesystem access (50)

⚙️ External commands (50)

🔑 Env variables (24)

⚡ Contains scripts (3)

patterns/test-doubles.md:186 patterns/test-doubles.md:199 quick-reference/jest-to-vitest.md:207

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/adammanuel-dev-vitest-testing/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/adammanuel-dev-vitest-testing/security.svg)](https://skillstore.io/skills/adammanuel-dev-vitest-testing?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/adammanuel-dev-vitest-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/adammanuel-dev-vitest-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/adammanuel-dev-vitest-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

AdamManuel-dev. (2026). vitest-testing security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/adammanuel-dev-vitest-testing/audits/10

BibTeX citation

@techreport{adammanuel-dev-adammanuel-dev-vitest-testing-2026,
  author = {AdamManuel-dev},
  title = {vitest-testing security audit report (audit version 10)},
  institution = {Skillstore},
  year = {2026},
  number = {10},
  url = {https://skillstore.io/skills/adammanuel-dev-vitest-testing/audits/10},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "vitest-testing security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
  - name: "AdamManuel-dev"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/adammanuel-dev-vitest-testing/audits/10"
identifiers:
  - type: other
    value: "skillstore:adammanuel-dev-vitest-testing:audit:10"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a new test suite

Choose the right mix of unit, integration, component, and E2E tests before implementation starts.

Improve brittle existing tests

Refactor tests around stable behavior, better fixtures, and focused assertions.

Migrate Jest patterns to Vitest

Map common Jest APIs and mocking techniques to Vitest equivalents with practical caveats.

Try These Prompts

Choose a test type

Use the vitest-testing skill to help me decide what kind of tests to write for this feature. Explain whether unit, integration, component, or E2E tests fit best.

Write focused Vitest tests

Use the vitest-testing skill to draft Vitest tests for this module. Follow AAA structure, test behavior, and include only necessary mocks.

Fix brittle tests

Use the vitest-testing skill to review these tests for brittleness. Suggest behavior-focused assertions, better fixtures, and safer async handling.

Design a testing strategy

Use the vitest-testing skill to design a Vitest strategy for this project. Cover test pyramid balance, test data management, mocks, integration boundaries, CI concerns, and migration risks.

Best Practices

Start from observable behavior before choosing mocks or implementation-level assertions.
Keep test data explicit, isolated, and reset between tests.
Use the smallest test type that gives confidence for the behavior under review.

Avoid

Do not copy examples that touch real databases, credentials, or services without test-only safeguards.
Do not overuse E2E tests for logic that unit or integration tests can cover faster.
Do not assert private implementation details when public behavior is available.

Frequently Asked Questions

Does this skill write complete tests for my project?

It provides patterns and prompts that guide an AI agent. The agent still needs access to your code and test runner.

Can it help with React Testing Library?

Yes. It includes component testing guidance for user events, accessibility queries, async rendering, and cleanup.

Does it support API and integration tests?

Yes. It covers API client tests, HTTP mocking, database boundaries, and integration test setup patterns.

Is it safe to copy every example directly?

No. Adapt examples to your test environment and avoid real credentials, production databases, or uncontrolled external services.

Can it migrate Jest tests to Vitest?

It includes Jest to Vitest guidance for common APIs, mocks, imports, and runner differences.

Does it replace manual test review?

No. Review generated tests for correctness, behavior coverage, security boundaries, and project-specific conventions.

Developer Details

Author

AdamManuel-dev

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/AdamManuel-dev/claude-code-ext/tree/main/skills/vitest-testing

Ref

7db9b9f06e0ab79c575b58bc48c4d8dc9849f424

Maintenance freshness

7/18/2026

Usage

6 downloads · 209 views

File structure

📁 patterns/

📄 api-testing.md

📄 async-testing.md

📄 component-testing.md

📄 e2e-testing.md

📄 error-testing.md

📄 integration-testing.md

📄 performance-testing.md

📄 test-data.md

📄 test-doubles.md

📁 principles/

📄 aaa-pattern.md

📄 bdd-integration.md

📄 first-principles.md

📄 testing-pyramid.md

📁 quick-reference/

📄 cheatsheet.md

📄 decision-tree.md

📄 jest-to-vitest.md

📁 refactoring/

📄 testability-patterns.md

📁 strategies/

📄 black-box-testing.md

📄 implementation-details.md

📄 index.md

📄 README.md

📄 SKILL.md

📄 STATUS.md

📄 SUMMARY.md

📄 TEST-SUITE-EXPLANATION.md

📄 user-service.test.ts

Build Starknet Apps with starknet.js

by internet-court

Starknet integrations require precise provider, account, transaction, and fee handling across several APIs. This skill provides focused starknet.js v9.x patterns for reliable TypeScript applications.

Coding & Development View

vitest-testing

Install with my Agent

Agent-readable resources

Test it

Security Audit

Confirmed security concerns (7)

Risk Factors

Copy report link

Markdown badge

HTML badge

Embed card

APA citation

BibTeX citation

CITATION.cff

Skillstore Score

What You Can Build

Plan a new test suite

Improve brittle existing tests

Migrate Jest patterns to Vitest

Try These Prompts

Best Practices

Avoid

Frequently Asked Questions

Developer Details

More from AdamManuel-dev

code-review

typescript-jsdoc

architecture-patterns

playwright-browser-automation

router

Related Skills

playwright-testing

testing

react-dev

senior-frontend

jest-testing

starknet-js