test-writer · vstorm-co — Claude Code skill: what it does, how to install
test-writer generates structured test suites for existing code matching your active testing framework.
MIT ★ 1,125 updated 2026-10-27
npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a claude-codeWhat test-writer does
This skill guides the model to examine target codebases, discover the established test runner such as pytest or unittest, and mirror existing project conventions. It focuses on isolating distinct behaviors so that each test function targets one specific scenario rather than an entire method.
Coverage spans standard execution flows, edge cases with empty containers or boundary numbers, explicit failure handling, and integration passes across multiple calls. External resources like network endpoints or databases are mocked out, while shared setup relies on fixtures.
Assertions demand exact value comparisons rather than plain truthiness checks. The skill strictly enforces the test_<what>_<condition>_<expected> naming pattern across all generated test files.
What it helps with
- generate full test coverage for existing source files
- verify edge cases including zero, empty lists, and boundary inputs
- mock external network or database calls in integration tests
Example prompts for the agent
- Write comprehensive tests for user_service.py using our current framework
- Add boundary and error test cases for the billing calculations
- Generate integration tests covering state changes across the order workflow
How to install test-writer
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a claude-code2Manually: put the files in place
~/.claude/skills/test-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/test-writer/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a codex2Manually: put the files in place
.agents/skills/test-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a cursor2Manually: put the files in place
.cursor/skills/test-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vstorm-co/pydantic-deepagents apps/cli/skills/test-writer2Manually: put the files in place
.github/skills/test-writer/SKILL.md1Skills CLI (Vercel)
npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/vstorm-co/pydantic-deepagents --path apps/cli/skills/test-writerManually: put the files in place
.devin/skills/test-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about test-writer
How to install test-writer in Claude Code?
Run npx skills add vstorm-co/pydantic-deepagents --skill test-writer -a claude-code or place the file directly at ~/.claude/skills/test-writer/SKILL.md.
What does test-writer do?
It instructs Claude Code to inspect public methods, adopt existing test conventions, and write suites covering normal paths, edge inputs, exceptions, and integrations.
What naming convention does test-writer enforce?
It formats test functions according to the test_<what>_<condition>_<expected> template, allocating one function per behavior.
Source text
SKILL.md · MIT
--- name: test-writer description: "Generate comprehensive test suites for existing code" tags: [testing, code-quality] version: "1.0.0" --- # Test Writer Generate comprehensive tests for the target code. ## Process 1. Read the source code to understand all public functions/methods 2. Identify the testing framework already used in the project (pytest, unittest, etc.) 3. Follow existing test patterns and conventions in the project 4. Write tests covering all categories below ## Coverage Strategy ### Happy Path - Normal inputs with expected outputs - All public methods/functions ### Edge Cases - Empty inputs (empty string, empty list, None) - Boundary values (0, -1, max int) - Single element collections ### Error Cases - Invalid input types - Missing required arguments - Network/IO failures (mock external calls) ### Integration - Multiple functions working together - State changes across calls ## Guidelines - One test function per behavior, not per method - Descriptive test names: `test_<what>_<condition>_<expected>` - Use fixtures for shared setup - Mock external dependencies (APIs, databases, filesystem) - Assert specific values, not just truthiness - Test both return values and side effects
© vstorm-co · MIT · vstorm-co/pydantic-deepagents
Similar skills
All skills for Testing and QA →test-writer by other authors comes first.