Gitnexus Refactoring

What it does

Gitnexus Refactoring automates complex code refactorings within Git repositories, aiming to improve maintainability and reduce technical debt. It assists with tasks like renaming symbols, extracting code into modules, splitting functions or services, and moving code to new files. The skill leverages a workflow that maps dependencies and execution flows before applying changes, ensuring safer and more controlled refactoring operations.

When to use it

This skill is helpful in the following situations:

• Renaming a function or symbol.
• Extracting a section of code into a separate module.
• Splitting a large function or service into smaller components.
• Moving code from one file to another within the repository.
• Any task involving restructuring existing code.

Key capabilities

• Automated Renaming: gitnexus_rename facilitates automated multi-file renaming with preview and application options.
• Dependency Mapping: gitnexus_impact identifies dependents of a target symbol or function, crucial for understanding the scope of changes.
• Execution Flow Analysis: gitnexus_query helps find execution flows involving specific code elements.
• Contextual Reference Exploration: gitnexus_context provides visibility into incoming and outgoing references to a given code element.
• Change Verification: gitnexus_detect_changes verifies that only the expected files have been modified after refactoring, assessing risk level.
• Custom Queries: gitnexus_cypher allows for custom reference queries using a cypher-like syntax.

Example prompts

Here are some example prompts you could give an agent with this skill:

• "Rename the function validateUser to authenticateUser and show me a dry run of the changes."
• "Extract the code related to user authentication into a new module."
• "What other functions call loginHandler?"

Tips & gotchas

• Stale Index: If you encounter an "Index is stale" error, run npx gitnexus analyze in your terminal.
• Review Carefully: While gitnexus_rename provides high-confidence graph edits, always carefully review the results of ast_search edits before applying changes.
• Test Thoroughly: Always run tests for affected processes after any refactoring operation to ensure functionality remains intact.