gitnexus-refactoring

Name: gitnexus-refactoring
Availability: InStock
Author: lortunate

Automate safe code refactoring by renaming, extracting, splitting, or moving symbols.

1|Updated Apr 12, 2026

Search Tags:#git #refactoring #dependencies #split #rename #code #extract

Ready to run

npx skills add https://github.com/Lortunate/CodexLAG --skill gitnexus-refactoring-lortunate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/Lortunate/CodexLAG/tree/main/.claude/skills/gitnexus/gitnexus-refactoring
Command: npx skills add https://github.com/Lortunate/CodexLAG --skill gitnexus-refactoring-lortunate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates safe code refactoring tasks by guiding and executing renames, extractions, splits, and moves across a codebase without breaking dependencies.

Core Features & Use Cases

Automated Rename Symbol: map dependents, update imports, and adjust references across files.
Extract/Split: create new modules or services with updated interfaces and calls.
Change verification: plan edits, apply changes, and run post-refactor validations.
Use Case: renaming a function used by multiple modules while preserving behavior and tests.

Quick Start

Plan and execute a safe refactor by using gitnexus_rename to rename a symbol, then gitnexus_impact to map callers, and gitnexus_detect_changes to verify all edits.

Frequently Asked Questions about gitnexus-refactoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I rename a function across multiple modules without breaking dependencies?▼

To rename a function safely without breaking dependencies, map dependents and callers, update imports, and adjust references across files before running post-refactor validations.

What is the best way to extract or split code into new modules?▼

Extracting or splitting code into new modules involves creating new services with updated interfaces and calls, mapping dependencies, and verifying changes to ensure all references remain intact.

How does automated refactoring verify changes after moving code?▼

Automated refactoring verifies changes by planning edits, applying symbol moves, and running post-refactor validations to detect changes and confirm tests pass across interdependent modules.

Can I use automated refactoring for large software projects with interdependent modules?▼

Yes, automated refactoring suits software projects with interdependent modules by mapping dependencies, applying edits across callers and imports, and verifying results across affected tests.

Why do I need to map dependencies before renaming a symbol in my codebase?▼

Mapping dependencies before renaming a symbol is required to identify all callers and imports that need updates, preventing broken references and ensuring behavior is preserved across the codebase.