Test Writer
Use this skill when the user wants high-signal unit tests from an existing source file or module.
Agent Compatibility
- Claude Code: supported
- Codex: supported
Inputs
- One or more source files
- Existing test style, helpers, and framework conventions when they exist
- Bug reports or regressions that the tests must lock in
Workflow
- Read the source file and nearby tests before writing anything.
- Infer the existing test framework and naming conventions.
- Cover the main behavior, edge cases, and failure paths.
- Prefer deterministic tests over brittle snapshots.
- Add only the smallest helpers needed to keep the tests readable.
Output Contract
- Explain the behavioral areas covered.
- Add or update tests in the repository's existing style.
- Mention untestable paths, hidden dependencies, or coverage gaps.
Guardrails
- Do not mock what the codebase already exercises cheaply with real objects.
- Do not encode internal implementation details when public behavior is enough.
- Do not stop at a happy-path test if error paths matter.