improve-ut

To increase unit test coverage, analyze changed files via git diff and generate or update tests that adhere to project specs. This automatically scaffolds focused tests and validates them using pnpm lint, typecheck, and test commands.

Yes, unit test generation requires a specific project structure. It applies to repositories that include .trellis/spec/ unit-test spec layers, respecting project conventions to select test scope and apply mock or real filesystem strategies.

Unit test scope selection works by analyzing git changes and package-specific unit-test spec layers. It determines whether to generate unit, integration, or regression tests based on the detected code modifications and project patterns.

The best way to scaffold tests after a bugfix is to analyze recent git changes and create or update tests according to existing project specs. This ensures tests follow current patterns and automatically reports remaining coverage gaps.

Mock strategies are handled by respecting project unit-test conventions during test generation. The process selects appropriate mock or real filesystem strategies based on the existing patterns found in the repository's test specifications.

The validation commands that run after generating unit tests are pnpm lint, pnpm typecheck, and pnpm test. These commands execute automatically to ensure newly scaffolded tests pass local validation and adhere to project standards.