review-duplication

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

Check package.json for installed libraries that already provide the functionality, then search utility directories like src/utils for existing implementations. Trace how third-party libraries are currently wrapped or used elsewhere in the project.

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

A good comment identifies the exact file path and symbol to reuse, provides a code snippet showing 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, services, configuration, and core logic. For components, use a generalist sub-agent to semantically compare the new implementation against existing components that could be extended or reused.