unit-test-coverage-push

What problem does it solve?

This Skill solves the problem of projects having high-priority (P0) user stories with no, partial, or E2E-only test coverage that blocks production shipping (violating red line 12), while avoiding fake or incomplete test work that wastes development time and creates false confidence.

Core Features & Use Cases

• 3-Step Systematic Playbook: Parse QA-TRACKER.md to count P0 US, classify each into derive/integration/deferred tiers, then generate and commit unit tests with full tracker sync.
• Multiple Test Patterns: Supports pure helper derivation for simple CRUD/validation logic, in-process integration testing for SSE/WebSocket/LLM routes, and proper deferred marking for untestable complex logic.
• Red Line Compliance: Enforces all QA red line rules, including scope confirmation with stakeholders, 5-point tracker sync, and blocker raising for impossible test scenarios.
• Use Case: For a backend project with 22 P0 US marked NONE/PARTIAL in QA-TRACKER, use this Skill to add 288 unit tests in 1-3 sprints, close all ship-blocker gaps, and reach 100% P0 unit test coverage without modifying source code.

Quick Start

Use the unit-test-coverage-push skill to add unit tests for all P0 user stories marked NONE or PARTIAL in your docs/QA-TRACKER.md file.