improve-ut

Analyze code changes to identify unit-test coverage gaps and update tests.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/alleneee/topsport-agent --skill improve-ut-alleneee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-ut
Source: https://github.com/alleneee/topsport-agent/tree/main/.agents/skills/improve-ut
Command: npx skills add https://github.com/alleneee/topsport-agent --skill improve-ut-alleneee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes code changes to identify gaps in unit-test coverage and applies project-specific unit-test conventions from .trellis/spec/ unit-test specs to guide improvements.

Core Features & Use Cases

  • Detects gaps in unit, integration, and regression test scopes based on code changes.
  • Adds or updates tests following existing patterns and project conventions.
  • Runs validation steps including lint, typecheck, and test suites to ensure quality.

Quick Start

Run improve-ut after code changes to automatically assess test coverage and update tests.

Frequently Asked Questions about improve-ut

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically detect unit test coverage gaps after code changes?

To detect unit test coverage gaps after code changes, you can run an automated refactoring tool that analyzes modified files and compares them against existing test scopes to identify missing unit, integration, and regression tests.

What is the best way to update unit tests to match existing project conventions?

The best way to update unit tests to match existing conventions is to apply project-specific unit-test specs, which read configuration files to guide test additions and ensure new tests align with established patterns.

How does applying unit-test specs improve code quality validation?

Applying unit-test specs improves code quality validation by defining the scope of required tests and executing lint, typecheck, and test suites, ensuring that code changes meet quality standards before integration.

Do I need project-specific configuration files to automate test updates?

Yes, you need project-specific unit-test specs stored in a designated directory to automate test updates, as these files provide the conventions and patterns necessary to guide the generation of new tests.

Can I use automated refactoring to determine if I need integration or regression tests?

Yes, automated refactoring tools can determine if you need integration or regression tests by analyzing the scope of code changes and applying configured unit-test specs to categorize the required validation level.

Why does my automated test validation fail after adding new unit tests?

Automated test validation may fail after adding new tests if the updates do not align with project specs or if lint, typecheck, and test suite execution detects type errors or convention violations in the new code.