.agents/skills/improve-ut/SKILL.md
Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.
npx skillsauth add basui01/agentflow improve-utInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to improve test coverage after code changes.
$improve-ut
Discover and read unit-test specs dynamically:
# Discover available packages and their spec layers
python3 ./.trellis/scripts/get_context.py --mode packages
Look for packages with unit-test spec layer in the output. For each discovered unit-test/ directory, read all relevant spec files inside it (for example index.md, conventions.md, integration-patterns.md, mock-strategies.md).
If this skill conflicts with the unit-test specs, the specs win.
git diff --name-onlypnpm lint
pnpm typecheck
pnpm test
## UT Coverage Plan
- Changed areas: ...
- Test scope (unit/integration/regression): ...
## Test Updates
- Added: ...
- Updated: ...
## Validation
- pnpm lint: pass/fail
- pnpm typecheck: pass/fail
- pnpm test: pass/fail
## Gaps / Follow-ups
- <none or explicit rationale>
development
Multi-agent pipeline orchestrator that plans and dispatches parallel development tasks to worktree agents. Reads project context, configures task directories with PRDs and jsonl context files, and launches isolated coding agents. Use when multiple independent features need parallel development, orchestrating worktree agents, or managing multi-agent coding pipelines.
development
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
development
Initializes an AI development session by reading workflow guides, developer identity, git status, active tasks, and project guidelines from .trellis/. Classifies incoming tasks and routes to brainstorm, direct edit, or task workflow. Use when beginning a new coding session, resuming work, starting a new task, or re-establishing project context.
development
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.