code-deduplication

To prevent semantic code duplication, you can maintain a centralized capability index that informs whether a new function should be created or an existing one extended. This check-before-write workflow ensures code reuse and reduces bloat.

A code deduplication audit identifies overlapping capabilities to reduce technical debt. Maintaining a CODE_INDEX.md tracks existing functions, enforcing a workflow where developers consult the index before implementation to reuse or extend code.

You enforce a check-before-write workflow by requiring developers to consult a CODE_INDEX.md before writing code. This index guides the decision to reuse, extend, or create new code, and must be updated post-implementation to stay auditable.

Yes, this deduplication approach is applicable to software engineering tasks involving writing or refactoring code. It focuses on deduplication checks, index updates, and post-write synchronization to maintain code hygiene across general development workflows.

The best way to maintain a capability index is to enforce explicit post-write synchronization. After implementing code, update the central CODE_INDEX.md to keep it current, ensuring future development can accurately check for reuse opportunities.

You should extend an existing function instead of creating a new one when a centralized capability index indicates overlapping capabilities. Consulting this index before implementation precludes semantic code duplication and bloat.