review-dry-violations

A repository-wide DRY audit analyzes your codebase to locate repeated UI patterns, scattered constants, and duplicated validation logic. It produces concrete evidence with file:line references and occurrence counts to prioritize extraction work.

The best way to find repeated Tailwind utility strings and badge color maps is a repository-wide DRY audit that groups similar shapes and counts occurrences. This provides concrete evidence to consolidate mappings into shared UI components.

Yes, you can track migration progress from mock data to real hooks. The DRY audit identifies mock-data usage across the codebase, providing file:line references and occurrence counts to guide safe extractions into shared utilities.

Yes, this DRY audit works with both frontend and backend validation logic. It is applicable to React frontend and Express/Prisma backend projects, performing repository-wide text analysis to locate overlapping validation and redundant types.

To get a markdown report of duplicated code patterns, run a DRY audit pass on the repository. It produces a report listing duplicated patterns with file:line references, suggested extractions, and estimated lines saved for refactor planning.