review-duplication

Extract the core logic from the new code, hypothesize where similar functionality would live in the project, then search the codebase for structural, naming, and documentation matches. Delegate deep searches to sub-agents for open-ended investigations.

Search utility directories like packages/core/src/utils/ for similar naming patterns and underlying APIs, and check package.json for installed libraries such as lodash or uuid that already provide the functionality.

Delegate any open-ended investigation, such as semantic comparisons or architectural mapping, to sub-agents like codebase_investigator. Reserve direct searches for simple unambiguous checks like verifying a dependency in package.json.

A good comment identifies the exact file path and symbol to reuse, shows a code snippet demonstrating how to integrate the existing implementation, and explains the benefit such as consistency or built-in edge case handling.

Yes, the workflow covers UI components by searching component directories and using a generalist sub-agent to semantically compare the new component against existing ones that could be extended or reused.