
Test Writer
This automates the tedious work of writing Vitest tests for code examples in documentation. It scans your concept pages, extracts every console.log and return value, then generates proper test files with source line references and organized describe blocks. The four phase approach handles everything from basic assertions to DOM tests, async code, and intentional errors. It follows project conventions like putting fundamentals tests in one directory and advanced topics in another, naming DOM tests with .dom.test.js, and structuring describe blocks to mirror your documentation sections. Best for maintaining a docs site where you need confidence that every code snippet actually works as shown.
- skills.sh installs
- 356
- GitHub stars
- 66.5K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add leonardomso/33-js-concepts --skill test-writer --agent claude-codeInstalls into .claude/skills of the current project.
Files
Skill: Test Writer for Concept Pages
Use this skill to generate comprehensive Vitest tests for all code examples in a concept documentation page. Tests verify that code examples in the documentation are accurate and work as described.
When to Use
- After writing a new concept page
- When adding new code examples to existing pages
- When updating existing code examples
- To verify documentation accuracy through automated tests
- Before publishing to ensure all examples work correctly
Test Writing Methodology
Follow these four phases to create comprehensive tests for a concept page.
Phase 1: Code Example Extraction
Scan the concept page for all code examples and categorize them:
Sponsors
Details
- Repository
- github.com/leonardomso/33-js-concepts
- Categories
- Testing & QA, Documentation
- First seen
- Jun 3, 2026