gitnexus-refactoring

To safely refactor code across repositories, you can rename, extract, or split components using deterministic steps, dry runs, and explicit change verification to prevent regressions. It analyzes targets, plans the refactor order, and propagates changes.

Planning code refactoring requires a deterministic order: interfaces first, then implementations, followed by callers, and finally tests. This structured approach minimizes risk by ensuring dependencies are updated systematically before executing the actual code modifications.

Yes, you can preview code modifications and run dry runs before applying changes. The refactoring process enforces iterative checks and explicit change verification during execution, allowing you to validate modifications safely without immediately altering your codebase.

Yes, relocating or splitting modules requires a GitNexus configuration to drive the workflow. This setup enables symbol-level edits, module extraction, and service splits across repositories while guiding the analysis and application of structural changes.

To prevent regressions during module extraction, the refactoring process uses iterative checks and explicit change verification. It enforces deterministic steps and previews, ensuring that all structural modifications are validated before being applied to the codebase.

Automated code refactoring for split and relocation tasks relies strictly on GitNexus configurations and deterministic steps. It does not apply changes without previews or dry runs, meaning unverified or non-explicit modifications outside this structured workflow are not supported.