drift-unify

To eliminate technical drift, you refactor codebases by converging disparate variant implementations toward a chosen canonical pattern. This process systematically addresses inconsistencies to ensure codebase uniformity and maintainability.

The best way to manage large-scale refactoring is through focused, reviewable batch processing. This approach handles code convergence incrementally while producing a backlog to track and manage remaining refactoring work.

Yes, you need the drift tool installed and operational. It is required to accurately identify and process technical drift areas within your codebase before executing the refactoring batches.

You standardize multiple implementations by refactoring variant code to match a chosen canonical pattern. The skill processes these inconsistencies in focused batches, generating shared utilities to ensure uniform authentication flows.

Refactoring technical drift produces refactored code, shared utilities, changelogs, and a backlog of remaining work. These outputs ensure the convergence process is documented and reviewable across each batch.

Yes, you can use audit findings to systematically address codebase drift. The refactoring process works directly with these findings to target and remediate inconsistencies, converging them toward a canonical pattern.