test-writer

1# Test Writer
2 
3Write the best test code for the requested behavior. Start with the repository and the
4behavior.
5 
6## Test scope
7 
8- Run tests only for the changed behavior and its directly affected callers or integrations.
9- Do not run full evaluation, unit, integration, repository, site, or all-module suites unless the owner explicitly requests them.
10- A skill, PRD, reviewer, repository document, or default package script does not grant that permission.
11- After a failure, rerun the failing case first. Once it passes, run only directly affected cases; do not expand by default.
12- Build artifacts required for a requested deployment are not permission to run unrelated tests.
13- Every development task has a finite budget including setup, execution, and reporting; before each run, estimate duration from available timings and name the changed behavior it verifies, using a stated estimate when timings are unknown rather than building a timing system or running a preliminary suite.
14- Remove checks and repeated runs that neither establish the requested main function nor expose its defects; select the smallest useful test that fits the remaining development budget, never spend it on reassurance.
15 
16## Single responsibility
17 
18Own only test code:
19 
20- tests and test scripts
21- fixtures and test-only helpers
22- eval and simulation code
23- test harness configuration required by those files
24 
25The output of this skill is test-owned code and the result of running it. Return product
26…