test-writer

Generate Vitest tests for JavaScript concept documentation code examples.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mwathiben/PropManager --skill test-writer-mwathiben
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-writer
Source: https://github.com/mwathiben/PropManager/tree/main/.claude/skills/test-writer
Command: npx skills add https://github.com/mwathiben/PropManager --skill test-writer-mwathiben

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning JavaScript concept documentation pages into fully tested code examples, reducing drift between docs and behavior and accelerating validation.

Core Features & Use Cases

  • Convert code examples in concept pages into Vitest tests that validate outputs and behavior.
  • Organize tests by documentation sections with references to exact source lines for traceability.
  • Generate both unit-style tests and DOM-related tests where applicable, following established Vitest conventions.

Quick Start

Translate a new or updated concept page into a set of Vitest-based tests with line-referenced comments and ready-to-run test files.

Frequently Asked Questions about test-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate Vitest tests for JavaScript documentation pages?

Auto-generate Vitest tests for JavaScript documentation by converting concept pages into ready-to-run test files, validating code examples and linking assertions to exact source lines for traceability.

What is the best way to test code examples in JavaScript documentation?

Testing code examples in JavaScript documentation is best handled by generating modular Vitest test files that validate behavior and output while referencing exact documentation lines for traceability.

Can I organize generated Vitest tests by documentation sections?

Yes, you can organize generated Vitest tests by documentation sections, producing modular describes with line-referenced comments that map test cases directly to their source concept pages.

Does this approach generate DOM-related tests for JavaScript concept pages?

Yes, the process generates both unit-style and DOM-related Vitest tests for JavaScript concept pages where applicable, ensuring comprehensive validation of code examples following established conventions.

Why do I need line-referenced comments in my generated Vitest test files?

Line-referenced comments in generated Vitest test files ensure traceability between test assertions and source documentation lines, preventing drift between concept page examples and actual behavior.