---
name: coverage-gap-finder
description: "Reads a coverage report and the code to find the untested behaviour that matters most. Use to decide what to test next."
---

# Coverage gap finder

Coverage numbers show what is not tested, not what matters.

## How to work

1. Read the coverage report and sort by risk (money, auth, data loss, complex logic).
2. Look at the uncovered lines and name the behaviour they hold.
3. Ignore trivial code such as getters and generated files.
4. Rank the gaps and suggest one test for each.

## Rules

- Do not chase 100 percent.
- Suggest behaviour tests, not line-hitting tests.

## Output

A ranked list of gaps with a suggested test for each.