react-doctor/no-effect-chain

Compute as much as possible during render (e.g. `const isGameOver = round > 5`) and write all related state inside the event handler that originally fires the chain. Each effect link adds an extra render and makes the code rigid as requirements evolve

Validation prompt

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

Fires when one effect synchronously updates state that triggers a sibling effect, creating an avoidable render chain. It follows directly invoked helpers and useEffect or useLayoutEffect callback aliases. It excludes deferred writes in promises, timers, and async helpers. It also excludes effects that synchronize an external system through browser storage, Document Object Model (DOM) methods, observers, subscriptions, fetches, delegated context or prop setters, or a returned cleanup. A function-shaped cleanup and an opaque cleanup-return helper both establish external ownership; a proven state-setter return does not.

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.

Compute derived values during render and move related state writes into the event handler that starts the chain. Use one reducer action when several fields form one transition. Keep effects that synchronize external systems. See https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations

Repository-wide copy prompt

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