Test health

Analyze the repository's current ability to detect important regressions, then choose one bounded improvement slice that makes future changes safer. Optimize for confidence and risk reduction—not test count, line coverage, or testing activity.

A slice has one primary risk or behavior, one main seam or test level, and the supporting setup and related scenarios needed to make the signal trustworthy. It is intentionally larger than a token one-test change when the evidence calls for it, but smaller than a broad testing campaign. This skill is a repository assessment and incremental-improvement playbook. It is not a mandate to use TDD everywhere, add tests for every file, migrate the testing stack, or make the repository fully tested in one run.

Principles

Apply these principles directly: