qa-unit

Audits unit tests against spec requirements and adds missing coverage.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-unit-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-unit
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/qa-unit
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-unit-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unit test suites often drift out of sync with the specification, leaving acceptance scenarios, edge cases, and functional requirements untested while other cases get duplicated. This Skill audits existing tests against the spec and adds only the missing coverage. ## Core Features & Use Cases - Spec-Driven Audit: Reads Acceptance Scenarios, Edge Cases, Functional Requirements, and Clarifications from specs/*/spec.md to build the authoritative list of what must be tested. - Gap-Only Test Generation: Reports scenarios already covered in tests/unit/ and writes new tests with real asserts only for uncovered items, avoiding duplication. - Verified Execution: Runs uv run pytest tests/unit/ -v and reports how many tests passed, failed, and were newly added. - Use Case: After implementing a feature with Spec Kit, run this Skill to confirm every acceptance scenario and edge case has a corresponding unit test before merging. ## Quick Start Audit my unit tests against the spec and add tests for any uncovered acceptance scenarios or edge cases.

Frequently Asked Questions about qa-unit

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

FAQPage Schema
How do I check if my unit tests cover all spec requirements?▼

Run this Skill to compare tests/unit/ against the Acceptance Scenarios, Edge Cases, and Functional Requirements in specs/*/spec.md. It reports which items are already covered and adds tests only for the gaps.

How to generate unit tests from a specification file?▼

The Skill parses specs/*/spec.md sections including Clarifications, maps each testable requirement to an isolated function, and writes new pytest tests with real asserts in the appropriate tests/unit/ file.

What happens if there is no spec file in the project?▼

The Skill stops and asks you to run Spec Kit first. It does not invent its own test criteria, since the spec is the authoritative source of what should be tested.

Does it duplicate tests that already exist?▼

No. It reviews existing tests in tests/unit/ first and reports covered scenarios as already covered in the specific file, adding tests only for uncovered requirements.

Can it add tests for cases not in the spec?▼

No. It only generates tests for scenarios explicitly in the spec. If it notices something important missing, it suggests it at the end instead of generating it autonomously.