Menu

Individual skill

test-generator

Creates meaningful unit, integration, and component tests based on implementation and requirements. Use when code needs test coverage and you want tests that verify behavior, not just tests that pad a coverage number.

skills/testing/test-generator/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Generate tests that actually verify behavior — correctness under normal input, boundary conditions, and failure modes — rather than tests that exist only to move a coverage percentage.

## When to Use

- Code has no tests, or existing tests don't cover the behavior that matters.
- Before refactoring, to lock in current behavior first.
- The user asks for tests for a specific function/module/component.

## What to Analyze / Do

1. **Understand actual behavior** — read the implementation (not just the function name/docstring) to know what it really does, including edge cases it may or may not handle.
2. **Cover the happy path** — normal, expected input produces the expected output.