Improve Unit Tests (UT)

Use this skill to improve test coverage after code changes.

Usage

$improve-ut

Source of Truth

Discover the available package spec layers dynamically:

# Discover available packages and their spec layers
python3 ./.trellis/scripts/get_context.py --mode packages

This repository currently has frontend, backend, and guides layers rather than a dedicated unit-test/ layer. Read:

• .trellis/spec/frontend/quality-guidelines.md for Vitest/frontend changes
• .trellis/spec/backend/quality-guidelines.md for Rust/backend changes
• existing colocated *.test.ts, *.test.tsx, and Rust module tests in the touched domain

If a package later introduces a dedicated test-spec layer, that package-local spec wins.

Execution Flow

1. Inspect changed files:
   • git diff --name-only
2. Decide test scope using the applicable quality spec and nearby test patterns:
   • unit vs integration vs regression
   • mock vs real filesystem flow
3. Add/update tests using existing project test patterns
4. Run validation:

npm run lint
npm run typecheck
npm run test

5. Summarize decisions, updates, and remaining test gaps.

Output Format

## UT Coverage Plan
- Changed areas: ...
- Test scope (unit/integration/regression): ...

## Test Updates
- Added: ...
- Updated: ...

## Validation
- npm run lint: pass/fail
- npm run typecheck: pass/fail
- npm run test: pass/fail

## Gaps / Follow-ups
- <none or explicit rationale>