test-writer

Generate runnable test files for newly added or modified code.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/findexu/finpack-claude --skill test-writer-findexu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-writer
Source: https://github.com/findexu/finpack-claude/tree/main/plugins/setup-finpack/template/skills/test-writer
Command: npx skills add https://github.com/findexu/finpack-claude --skill test-writer-findexu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent regressions by turning recent code changes into a complete set of runnable tests that cover happy paths, edge cases, error handling, and integration behavior.

Core Features & Use Cases

  • Change discovery: Identifies what was added or modified via diff review and then maps behavior to testable units.
  • Comprehensive scenario planning: Covers happy paths, edge cases, null/undefined/nil handling, type boundaries, error paths, concurrency, state transitions, and integration points.
  • High-quality test authoring: Produces complete runnable test files with descriptive test names, one-assertion-per-test discipline, and Arrange-Act-Assert structure.

Quick Start

Ask the test-writer skill to write tests for the code that was changed in this commit or pull request, using the project’s existing test framework conventions.

Frequently Asked Questions about test-writer

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

FAQPage Schema
How do I generate unit and integration tests for new code changes?

Generate unit and integration tests for new code changes by analyzing the git diff to identify modified behavior, then mapping those changes to testable units with happy paths, edge cases, and error handling.

What is the best way to increase test coverage for a recent refactor?

To increase test coverage for a recent refactor, map the modified code to comprehensive scenarios including null handling, type boundaries, and state transitions, producing runnable test files that verify the refactored behavior.

How do I write tests that cover edge cases and async behavior automatically?

Cover edge cases and async behavior automatically by generating test files with strict mocking rules at system boundaries, ensuring one-assertion-per-test discipline and Arrange-Act-Assert structure for concurrent operations.

Does test generation work with existing project test frameworks and conventions?

Test generation works with existing project frameworks by producing complete, runnable test files that follow your project's conventions, applying scenario mapping and failure validation across pure functions, API handlers, and database layers.

How do I verify my new tests actually fail when the code is broken?

Verify new tests actually fail when code is broken through failure validation, a process that intentionally breaks the modified code to confirm the generated tests catch regressions before restoring the correct implementation.