react-doctor/exhaustive-deps

Match the deps array to what the hook callback actually captures, or stabilize/move recreated values instead of blindly adding them.

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on useEffect, useLayoutEffect, useInsertionEffect, useCallback, useMemo, useImperativeHandle, and configured additional hooks when the dependency array omits a reactive capture or contains an invalid dependency. Effects may intentionally omit the array, and unused reactive effect dependencies are allowed. useMemo and useCallback require dependency arrays and report unused dependencies. All supported hooks report duplicates, spreads, literals, computed members, ref.current, useEffectEvent, inline-recreated values, and outer-variable assignments. Stable setters, dispatch, startTransition, ref bindings, effect-event handlers, module imports, and primitive local constants do not need dependencies.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

• Confirmed failure: The required evidence establishes the violation.
• Rejected: A documented exception or false-positive predicate applies.
• Needs evidence: Named evidence can still be collected.
• Unavailable: Required evidence cannot be collected in this run.
• Waived with evidence: An authorized, scoped exception applies to an established failure.
• Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Add every reactive capture when you provide a dependency array. Keep the required arrays on useMemo and useCallback; an effect may intentionally run after every render without one. Move recreated values into the callback or stabilize them before adding them. Use functional state updates to remove captured state, depend on the ref instead of ref.current, and avoid spreads or computed expressions. Add a narrow suppression with a written reason only when exclusion is intentional. See https://oxc.rs/docs/guide/usage/linter/rules/react/exhaustive-deps

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.