test-writer

Generate unit, integration, and component tests with mocks for untested code paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically analyzes code to identify untested paths and generates unit, integration, and component tests with proper mocking and edge-case coverage.

Core Features & Use Cases

  • Analyze code for untested paths and generate unit, integration, and component tests with proper mocking and edge-case coverage.
  • Produce test suites for unit, integration, and UI/components where applicable.
  • Enable rapid test expansion as the codebase evolves and requirements change.

Quick Start

Tell Test Writer which files or modules to test and it will generate the corresponding tests.

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 unit and integration tests for untested code paths?

You can auto-generate unit and integration tests by targeting specific files or modules to identify untested code paths and produce ready-to-run test suites with proper mocking and edge-case coverage.

Can I generate component tests with mocks for my existing project?

Yes, component tests with mocks can be generated by specifying your language, framework, and test runner, ensuring the output aligns with your project's existing conventions and test structure.

What is the best way to expand code coverage as my codebase evolves?

The best way to expand code coverage is to analyze code for untested paths and rapidly generate unit, integration, and component test suites, prioritizing critical areas to match changing requirements.

Does test generation work if I specify my existing test runner and framework?

Yes, test generation works when you specify your existing test runner, language, and framework, allowing the tool to output structured test suites that align directly with your project's conventions.

How do I prioritize edge-case coverage for critical modules in my codebase?

To prioritize edge-case coverage for critical modules, apply the test generator to targeted files and specify those critical areas, which produces structured test suites focusing on untested paths.