improve-ut

Analyze changed files and unit-test specs to update and validate tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams improve unit test coverage after code changes by guiding a structured testing workflow and ensuring tests align with project conventions.

Core Features & Use Cases

  • Inspect changed files to determine scope and priorities.
  • Decide test scope (unit, integration, regression) using unit-test specs and project conventions.
  • Add/update tests using existing project test patterns and conventions.
  • Run validation: lint, typecheck, and tests, and surface follow-up gaps.

Quick Start

Invoke the UT improvement workflow to scan your recent changes, determine the appropriate test scope, update tests accordingly, and run the project validation suite.

Frequently Asked Questions about improve-ut

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

FAQPage Schema
How do I improve unit test coverage after making code changes?

Improve unit test coverage by analyzing changed files against unit-test specs to find gaps, then applying appropriate test scopes and mock strategies to update tests and validate results.

When do I need to use mocks vs real filesystem flows in unit tests?

Use mocks or real filesystem flows in unit tests by comparing changed files against unit-test specs, which helps decide the test scope and whether mocking strategies or real flows fit the project patterns.

How do I decide test scope between unit, integration, and regression testing?

Decide test scope by comparing changed files against unit-test specs and project conventions, which determines whether unit, integration, or regression tests are needed to cover the modifications.

What's the best way to validate code changes and surface follow-up test gaps?

Validate code changes and surface follow-up gaps by running lint, typecheck, and tests after updating unit tests, ensuring the modifications align with existing project patterns and surfacing remaining coverage gaps.

Does this unit test workflow work with existing project test patterns?

Yes, this unit test workflow executes updates by following existing project test patterns and conventions, ensuring newly added tests integrate seamlessly with the current testing setup.

Why are my unit tests not covering recently modified code files?

Unit tests miss modified code when changed files are not analyzed against unit-test specs, which is required to identify coverage gaps, apply mock strategies, and update the test suite accordingly.