Assess where a codebase's tests are thin and prioritize the tests that would actually reduce risk — use when coverage numbers are unclear or gamed, before a risky refactor or release, when the user asks "what should we test next", or to turn a raw coverage report into a ranked, meaningful test plan rather than chasing a percentage.
