consolidate

Fix code drift by running a consolidation pass that audits your Go source files against project conventions and automatically updates them for consistency. This reduces rework and drift-induced bugs before tagging a release.

Run a code consolidation pass after three or more sessions since your last alignment, before tagging a release, or when a session touched many files. This timing ensures conventions are enforced when drift is most likely to accumulate.

Enforce Go code conventions automatically by triggering a consolidation pass that implements and runs baseline convention checks. It audits your repository and updates files to align with project standards before you tag.

Consolidating source code requires a clean working tree and passing tests as preconditions. The process validates these states before performing any convention alignment changes to ensure safe integration.

Yes, code consolidation reduces rework by running baseline audits for lint and convention checks, then updating files to align with project standards. This catches drift-induced issues early rather than during later review stages.

Code-level drift is the inconsistency that accumulates between development sessions. Consolidation fixes it by auditing your codebase against project standards and automatically updating files to restore convention alignment.