gitnexus-refactoring

Plan multi-file code refactors with dependency mapping and dry-run previews.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shysssthanhtri/AI-tools --skill gitnexus-refactoring-shysssthanhtri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-refactoring
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/gitnexus-refactoring
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill gitnexus-refactoring-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables safe, discoverable, and auditable refactors across a codebase by mapping dependents, previewing automated edits, and verifying scope to reduce breakage and regressions during renames, extractions, moves, or splits.

Core Features & Use Cases

  • Automated multi-file renames with dry-run previews and confidence annotations for each edit type.
  • Impact analysis that maps upstream dependents, callers, and execution flows to plan update order and minimize disruption.
  • Change detection that lists affected files and processes and highlights low-confidence ast_search edits for manual review.
  • Use Case: Rename a widely-referenced function, extract a module while updating imports, or split a service into smaller functions while ensuring tests and callers are updated in the correct order.

Quick Start

Perform a dry-run rename of validateUser to authenticateUser, review all low-confidence edits and impacted callers, then apply changes and run relevant tests.

Frequently Asked Questions about gitnexus-refactoring

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

FAQPage Schema
How do I safely rename a function that has multiple callers across different modules?

To safely rename a function with multiple callers, use automated multi-file refactoring to map upstream dependents, preview edits via dry-run, and annotate confidence levels for each change before applying updates and running tests.

What is impact analysis in the context of code refactoring?

Impact analysis in code refactoring maps upstream dependents, callers, and execution flows to plan the correct update order, minimizing disruption and regressions during multi-file renames, extractions, moves, or splits.

How do I extract a module and update imports without breaking existing code?

To extract a module and update imports safely, perform a dry-run preview to detect affected files, review low-confidence ast_search edits for manual verification, and ensure tests and callers are updated in the correct order.

Can I preview automated code refactoring changes before applying them to my repository?

Yes, you can preview automated code refactoring changes using a dry-run, which lists affected files, highlights edit types with confidence annotations, and detects unintended file changes before you apply them.

What are the limitations of automated refactoring for mixed static and dynamic references?

For mixed static and dynamic references, automated refactoring may produce low-confidence ast_search edits that require manual review and test execution to ensure scope accuracy and prevent unintended breakage.