Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use this skill to improve test coverage after code changes.
$improve-utDiscover and read unit-test specs dynamically:
# Discover available packages and their spec layers
python3 ./.trellis/scripts/get_context.py --mode packagesLook for packages with unit-test spec layer in the output. For each discovered unit-test/ directory, read all relevant spec files inside it (for example index.md, conventions.md, integration-patterns.md, mock-strategies.md).
If this skill conflicts with the unit-test specs, the specs win.
git diff --name-onlypnpm lint
pnpm typecheck
pnpm test## UT Coverage Plan
- Changed areas: ...
- Test scope (unit/integration/regression): ...
## Test Updates
- Added: ...
- Updated: ...
## Validation
- pnpm lint: pass/fail
- pnpm typecheck: pass/fail
- pnpm test: pass/fail
## Gaps / Follow-ups
- <none or explicit rationale>202780181/lingxiData
83191c9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.