Vitest 3 Features
CheckedAutomates Vitest tests, ensuring JavaScript component functionality aligns with specified features and expectations.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add josiahsiegel/claude-plugin-marketplace --skill vitest-3-features -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
josiahsiegel
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5a1b1123b9
- Scanned
- 1 file, 522 lines
About this skill
What it does
This skill provides comprehensive knowledge of Vitest 3.x features and modern testing patterns, focusing on improvements released since January 2025. It enables AI agents to automate Vitest tests, specifically leveraging new capabilities like the Annotation API, Line Number Filtering, and Enhanced Watch Mode for JavaScript component functionality. The skill also includes guidelines for file path handling on Windows systems.
When to use it
- When needing to add custom metadata, messages, or attachments to test results (e.g., debugging information, links to external resources).
- To execute specific tests directly from an IDE by line number.
- For faster and more accurate test execution during development with improved change detection in watch mode.
- When working on Windows systems and needing to ensure correct file path formatting.
Key capabilities
- Annotation API: Allows adding custom metadata, messages, and attachments to tests for reporting across various formats (UI, HTML, JUnit, TAP, GitHub Actions).
- Line Number Filtering: Enables running specific tests by their line number within a file.
- Enhanced Watch Mode: Provides smarter change detection, faster rebuilds, and improved file watching, especially on Windows.
- Windows File Path Handling: Enforces the use of backslashes (
\) in file paths when using Edit or Write tools on Windows systems.
Example prompts
- "Add an annotation to this test indicating it's testing OAuth2 flow with external provider and attach the oauthConfig."
- "Run the test located at line 42 of tests/user.test.js."
- "How do I configure watch mode in Vitest?"
Tips & gotchas
- Windows File Paths: Always use backslashes (
\) when specifying file paths on Windows systems within Edit or Write tools. For example,D:\repos\project\file.tsxinstead ofD:/repos/project/file.tsx. - Documentation: The skill prioritizes updating existing documentation rather than creating new files.