react-doctor/jsx-no-undef

Import the component or fix the typo so the JSX element name resolves to a real binding.

Validation prompt

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

Fires on a JSX opening element whose name resolves to an identifier with no binding in scope: a capitalized plain tag (<App />, <Foo />), or the ROOT object of a member expression regardless of case (<App.Foo />, <appp.foo.Bar /> both fire when the root is unbound). Lowercase intrinsic tags (<img />, <x-gif />), namespaced names (<Foo:Bar />), and the known globals globalThis/window/document/console/React/self/this are skipped.

Suppress when: scope resolution is best-effort: shadowing and same-name imports from multiple modules are approximated, so a name bound somewhere reachable may be accepted even when the chosen binding is wrong; confirm the intended import or declaration actually exists before treating a report as a genuine typo.

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.

Import the missing component or fix the typo so the element name resolves: add the import (import App from './App') or correct the spelling (<Appp /> -> <App />). For member expressions, ensure the root object is in scope: import the namespace, e.g. import * as Icons from './icons' for <Icons.Star />. If you actually meant an intrinsic/custom HTML element, lowercase the tag name so it is treated as an intrinsic tag rather than a (capitalized) component reference. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-no-undef

Repository-wide copy prompt

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