test-coverage-analyzerlisted

# Test Coverage Analyzer This skill helps identify gaps in test coverage and suggests specific test cases to improve code quality. ## When to Use This Skill - User asks to analyze test coverage - User wants to improve test coverage - User requests suggestions for missing tests - Working on increasing code coverage percentage - User mentions "coverage gaps", "untested code", or "test suggestions" ## Instructions ### 1. Detect Testing Framework Identify the testing framework(s) used in the project: **JavaScript/TypeScript:** - Jest: `jest` in package.json or `jest.config.js` - Mocha: `mocha` in package.json or `.mocharc` - Vitest: `vitest` in package.json or `vitest.config.js` - Jasmine: `jasmine` in package.json **Python:** - pytest: `pytest` in requirements.txt or `pytest.ini` - unittest: Standard library, check for test files - coverage.py: `coverage` in requirements.txt **Ruby:** - RSpec: `rspec` in Gemfile - Minitest: Standard library **Go:** - Built-in: `go test` (coverage via `go test -cover`) **Java:** - JUnit: Look for JUnit in pom.xml or build.gradle - JaCoCo: Coverage tool configuration Use Glob and Grep to find configuration files. ### 2. Locate Coverage Reports Find existing coverage reports: **Common locations:** - `coverage/` directory - `.nyc_output/` (NYC for Node.js) - `htmlcov/` (coverage.py for Python) - `target/site/jacoco/` (JaCoCo for Java) - Coverage files: `lcov.info`, `coverage.json`, `.coverage` **If no coverage report exists:** - Guid