Review test coverage and regression risk

Use this prompt after a code, API, configuration, fixture, mock, or test change to identify what behavior is covered, what is missing, and where regression risk still needs verification.

Outcome
A focused test-impact review
Produces coverage gaps, regression risks, weak assertions, missing setup evidence, and concrete test additions.
Use case
Post-change verification
Use after implementation, configuration, API, fixture, mock, or test changes that may affect expected behavior.
Output
Required tests and risk areas
Returns required test additions, optional improvements, missing evidence, and confidence level.

Scope and best-fit use

Use this prompt to turn a code or configuration change into a focused test-impact review: covered behavior, missing scenarios, weak assertions, setup gaps, and regression-sensitive paths.

Use when
You need to verify testing impact after a change
Use it when changed behavior, configuration, fixtures, mocks, API contracts, or test setup may require new or updated tests.

Use this as a runtime review prompt

Paste the current change materials into the prompt. Keep stable team review rules in the instruction layer, such as project instructions, GPT instructions, Claude project instructions, Gemini Gems, or API system instructions.

Inputs required

Provide the changed behavior and the test evidence needed to evaluate coverage. The prompt should not infer test results, coverage numbers, logs, or defects that were not supplied.

Change context
Goal, changed files or excerpts, affected behavior, API or interface changes, configuration changes, environment details, and known constraints.
Test evidence
Relevant test files, fixtures, mocks, test data, assertions, setup and cleanup logic, logs, coverage output, and known regression-sensitive paths.

Copy-ready prompt

Copy the prompt and replace the MATERIALS block with the current change, tests, configuration, logs, and coverage evidence. 

Run a test coverage and regression-risk review.

TASK:
Review the supplied materials and identify:
- behavior that is covered by existing tests
- behavior that is not covered
- weak or missing assertions
- fixture, mock, test-data, setup, cleanup, or configuration gaps
- regression-sensitive paths that need verification

REVIEW SCOPE:
Focus on testing impact, coverage gaps, regression risk, and verification planning.
Only discuss architecture, standards, or security when they directly affect test coverage or regression risk.

EVIDENCE RULES:
- Base findings only on the supplied materials.
- Do not invent tests, logs, coverage numbers, execution results, defects, or pass/fail status.
- Mark unsupported findings as INSUFFICIENT_EVIDENCE.
- Separate verified findings from missing evidence.

CHECK:
- Behavior under test
- Positive paths
- Negative paths
- Edge and boundary cases
- Error paths
- Authentication and authorization paths, when relevant
- Integration points, when relevant
- Fixtures, mocks, test data, setup, and cleanup
- Regression-sensitive behavior

OUTPUT:
A) Context snapshot
B) Supplied test evidence
C) Covered behavior
D) Coverage gaps
E) Regression risks
F) Required test additions
G) Optional test improvements
H) Missing evidence
I) Confidence

MATERIALS:
"""
Replace this block with the current change context, implementation excerpts, tests, fixtures, configuration, logs, coverage output, and known regression-sensitive paths.
"""

Related code-review workflow

Use the guide and policy to decide when this testing-impact prompt is the correct review path.