dry-violations

To find duplicate enums and hardcoded values, this skill scans your codebase using static-analysis heuristics to flag repeated constants and domain logic, then suggests canonical centralized definitions for refactoring.

DRY violations are repeated hardcoded values, duplicate enums, and redundant domain logic across files. They degrade code maintainability by scattering definitions, making centralized updates and architectural audits difficult.

Yes, you can use static analysis to detect repeated domain methods during code reviews. It analyzes cross-file duplications in constants and type definitions, suggesting centralization to prevent duplication proactively.

The best way to scan for cross-file duplications in constants and type definitions is running a static-analysis scan that identifies repeated values and suggests a single canonical definition to centralize the logic.

Yes, DRY violation detection works for CI integration. The scan outputs are suitable for continuous integration pipelines, flagging duplicates and hardcoded values during feature development or automated audits.

You should not use automated DRY violation scans when a codebase lacks stable domain methods or enums, as heuristic static analysis may surface false positives for intentional repetitions in distinct type definitions.