improve-ut

You automate unit-test coverage by analyzing changed files and aligning new tests with project-specific unit-test specs. The tool identifies coverage gaps, determines whether to apply unit, integration, or regression tests, and updates tests following existing conventions.

You determine test scope by analyzing the nature of the changed files against project conventions. The tool evaluates observed changes from feature additions, bug fixes, or refactors to automatically decide whether unit, integration, or regression tests are required.

You update tests after a bug fix by scanning the changed files and adding targeted regression tests. The tool aligns the new tests with the project's unit-test specs and runs validation to ensure the fix is protected against future regressions.

Yes, you need the `.trellis/spec/` directory structure in your codebase. The tool specifically applies to codebases containing these unit-test specs to identify conventions and determine the correct testing scope.

Yes, you validate code changes by running lint, typecheck, and test suites in sequence. The tool automatically runs these validation checks after updating tests, summarizing decisions, updates, and any remaining coverage gaps.

The best way to align tests with new behavior is to scan the changed files and generate matching test updates. The tool applies project-specific conventions to add or update tests, ensuring full coverage and validation of the new feature.