test-coverage-lens

Assess test coverage and testing strategy for code changes.

30|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/atomicinnovation/accelerator --skill test-coverage-lens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-coverage-lens
Source: https://github.com/atomicinnovation/accelerator/tree/main/skills/review/lenses/test-coverage-lens
Command: npx skills add https://github.com/atomicinnovation/accelerator --skill test-coverage-lens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineering teams determine whether a codebase's tests provide real, maintainable confidence by identifying missing coverage, weak assertions, and unreliable test architecture that could allow regressions to slip into production.

Core Features & Use Cases

  • Coverage adequacy: Detect missing tests for new code paths, untested error cases, and absent regression tests for bug fixes.
  • Test quality & assertions: Evaluate whether tests assert behaviour (not implementation), are specific, meaningful, and would fail under simple mutation.
  • Test architecture & reliability: Assess pyramid balance, isolation, mock strategy, flakiness, and whether tests are practical for CI pipelines.
  • Use Case: Before merging a feature branch, produce a prioritized report of missing or weak tests, estimate confidence, and recommend concrete tests to add.

Quick Start

Review the test suite for the proposed changes and produce a prioritized list of missing tests, flaky areas, and specific recommendations.

Frequently Asked Questions about test-coverage-lens

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

FAQPage Schema
How do I check if my test coverage catches real regressions before merging?

Assess test coverage and strategy by analyzing code changes to identify missing tests, weak assertions, and flaky patterns. Generate a prioritized report estimating regression confidence and recommending specific tests to add before merging.

What is the best way to find weak or assertion-free tests in a code review?

Evaluate test quality during code reviews by checking if tests assert behavior rather than implementation. Identify weak or assertion-free tests that would pass under simple mutation, then prioritize remediation based on assigned confidence levels.

How do I identify flaky patterns and over-mocking in my test suite?

Assess test architecture and reliability by evaluating pyramid balance, isolation, and mock strategy. Identify flaky patterns and over-mocking issues that make tests impractical for CI pipelines, then assign remediation priority.

Does test coverage analysis work for CI pipelines and release preparation?

Test coverage analysis applies to CI pipelines and release preparation where regression protection is needed. It identifies missing tests for new code paths, untested error cases, and absent regression tests for bug fixes.

How do I ensure tests assert behavior and would fail under mutation testing?

Evaluate whether tests are specific and meaningful by checking if they would fail under simple mutation. Tests should assert behavior rather than implementation details to provide real confidence against regressions.

Why does test coverage analysis prioritize missing tests for bug fixes?

Test coverage analysis prioritizes missing regression tests for bug fixes because untested error cases allow regressions to slip into production. Identifying absent tests ensures maintainable confidence in the codebase.