test-coverage-review

To generate missing tests for uncommitted code, invoke the skill to scan your git changes and automatically produce the necessary unit, integration, and E2E test files. It identifies new or modified functions lacking coverage and creates matching tests before you commit.

Yes, you can scope test generation to specific file paths or analyze the entire repository. Scoping to specific files ensures comprehensive validation of new logic while keeping the test generation process focused and efficient.

Yes, test generation requires integration with project-specific test runners like pytest, Jest, and Playwright. The skill learns your project's testing conventions and mocking patterns to ensure generated tests match your existing codebase.

To prevent regressions, the skill runs full-suite verification by executing both unit and E2E test suites after generating new tests. This automated verification ensures that newly generated tests pass and no existing functionality is broken.

Automating test coverage gap analysis involves scanning uncommitted git changes to identify new components, functions, and API routes that lack corresponding tests. The skill automatically performs this gap analysis and generates the required test files.

Unit, integration, and E2E tests are generated for untested code changes. The skill identifies new or modified functions lacking coverage and creates the appropriate test layers to ensure comprehensive validation across your project.