component-check

To enforce shadcn/ui usage in React components, you validate frontend code by identifying and replacing raw HTML elements like <button> and <input> with shadcn/ui counterparts. This workflow reports violations and suggests precise fixes while preserving behavior.

The best way to replace raw HTML with shadcn/ui counterparts in a pull request is by running an automated lint check that verifies element imports, detects non-compliant HTML tags, and generates a violation report with recommended safety-preserving changes.

Your React component validation reports missing shadcn/ui imports because the validation process actively verifies correct component imports and resolves missing or incorrect usages. It flags raw HTML elements that lack the required shadcn/ui library imports.

Yes, you can use this component validation workflow for automated lint checks across your frontend codebase. It applies to code review processes and pull requests by detecting raw HTML elements and generating violation reports with recommended fixes.

To identify raw HTML usage in React components, you run a validation check that detects elements like <button>, <input>, and <div> that should be replaced with shadcn/ui components. It verifies element imports and reports these violations.