impl-reuse-scan

Scanning for reusable assets identifies existing API routes, DTOs, and UI components within a codebase by analyzing task descriptions, preventing redundant implementation before starting new feature development.

Codebase reuse scanning identifies existing common assets like components and utilities before development. You need it during phase-based workflows to verify existing infrastructure, ensuring code consistency and reducing technical debt.

Prevent duplicate code by running automated discovery scans that check for existing API routes, DTOs, and UI components matching your task description, providing decision-making support to reuse rather than rebuild.

Yes, you can check for existing UI components and DTOs by scanning the codebase against your task description. The scan reports matching strength as identical, similar, or reference to support reuse decisions.

Automated discovery reports matching strength by categorizing existing code assets as identical, similar, or reference matches. This structured report facilitates a decision-making interview to determine reuse viability.

Codebase reuse scanning is limited to phase-based development workflows and depends on accurate task descriptions. It focuses on discovering existing API routes, DTOs, and UI components rather than automatically refactoring or modifying the identified redundant code.