unit-test-coverage

name	unit-test-coverage
description	Audit unit-test coverage gaps and generate new tests to improve confidence on critical paths. Use when asked to "improve test coverage", "find untested code", "write missing unit tests", "audit test coverage", or "increase coverage". Technology-agnostic.
disable-model-invocation	true
metadata	{"author":"olivomarco","version":"1.0.0","argument-hint":"<path-or-area-to-cover>"}

Unit Test Coverage Audit & Enhancement

Mission

Analyze the existing unit-test suite, identify coverage gaps (prioritizing business-critical and security-sensitive code), and generate new tests that meaningfully improve confidence. This skill writes tests — but never weakens or alters production code to make tests pass.

Scope & Preconditions

• If the user names an area, scope there; otherwise cover the primary source.
• Detect the test setup first: find the test runner and coverage tool from manifests/config (e.g. Jest/Vitest/Mocha, pytest, go test, JUnit, RSpec, PHPUnit) and the command used to run them. If you cannot determine the commands, ask the user before proceeding.
• Read existing tests first — they are the canonical style guide for structure, naming, mocking, and fixtures. Match them.
• Read any testing docs/instructions in the repo before writing tests.

Workflow

Phase 1 — Coverage Baseline

1. Run the project's coverage command and capture the output. If no coverage tool exists, derive coverage manually by mapping source units to existing tests.