sage-existence-review

To detect duplicate React components and SCSS partials in a design system diff, review newly added files in conventional directories to determine if a fresh artifact duplicates an existing one. This yields actionable prompts for extending or refactoring instead of duplicating surface artifacts.

The best way to prevent design token duplication during code review is to analyze new token keys in the diff to determine if they duplicate existing assets. This process yields concrete recommendations for extending current assets to maintain a single source of truth.

Yes, you can surface refactoring suggestions for sage-lib diffs in a pull request by analyzing the newly added files to flag artifacts that duplicate existing components, mixins, or styles. It proposes whether to extend a current asset or consolidate duplicates.

Yes, this existence review process works with newly added files in conventional directories. It analyzes these specific new files and new token keys to determine if a fresh artifact duplicates an existing one, providing actionable prompts for extending or refactoring instead of duplicating.

To consolidate duplicate design system styles to maintain a single source of truth, review diffs to identify duplicating artifacts and apply the recommended consolidation actions. This proposes extending a current asset rather than maintaining duplicate surface artifacts.

You should extend an existing component instead of creating a new one in sage-lib when a diff review identifies that a fresh artifact duplicates an existing asset. This yields actionable prompts recommending extension or refactoring to prevent surface artifact duplication.