What problem does it solve?
This Skill reduces the risk of regressions and low test coverage after code changes by analyzing modified files and applying project-specific unit-test conventions located in .trellis/spec. It ensures tests follow existing patterns and that validation steps run consistently so maintainers can trust CI results.
Core Features & Use Cases
- Spec-driven scope detection: Reads .trellis/spec unit-test layers to decide unit vs integration vs regression scope and whether to use mocks or real filesystem flows.
- Automated test updates: Adds or updates tests following repository test patterns, mock strategies, and integration patterns to preserve consistency.
- Validation and reporting: Executes project validation commands and summarizes lint, typecheck, and test outcomes along with remaining test gaps.
- Use Case: After implementing a new feature or fixing a bug in a Go monorepo, run this Skill to discover affected packages, generate or adjust tests per spec, and validate before merging.
Quick Start
Run the improve-ut skill to analyze changed files, update or add tests per .trellis/spec conventions, and validate changes with pnpm lint, pnpm typecheck, and pnpm test.