
Gitnexus Refactoring
This handles the hard part of refactoring: tracking down every place a symbol is used before you rename or move it. It maps dependencies with gitnexus_impact, then runs automated renames across multiple files with confidence scoring (graph-based edits are safe, AST search results need review). The workflow is structured around impact analysis first, then execution, then verification with detect_changes to see what you actually touched. Most useful when you're renaming something with more than five callers or extracting code that's referenced across different areas of the codebase. The dry run mode is smart since you can preview edits before committing to them.
- skills.sh installs
- 1.8K
- GitHub stars
- 48.4K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add abhigyanpatwari/gitnexus --skill gitnexus-refactoring --agent claude-codeInstalls into .claude/skills of the current project.
Files
Refactoring with GitNexus
When to Use
- "Rename this function safely"
- "Extract this into a module"
- "Split this service"
- "Move this to a new file"
- Any task involving renaming, extracting, splitting, or restructuring code
Bind the repository first
Refactoring writes to disk. rename with dry_run: false edits files in
whichever repository was resolved, so binding identity here is a safety gate,
not bookkeeping.
Call list_repos {} before the first tool call. With one indexed repository,
use the examples below as written. With more than one, pass repo on every
call: an omitted repo normally errors, but under an MCP policy with a
configured default it resolves to that default silently. If you cannot tell
which repository is meant, stop and ask. Never run rename with
dry_run: false until the preview in the same bound repository has been
reviewed — its returned file_path values show which checkout is about to be
written, so read them as a confirmation of identity.
list_repos is paginated, so page with offset: pagination.nextOffset until
hasMore is false before concluding a repository is absent.
Sponsors
Details
- Repository
- github.com/abhigyanpatwari/gitnexus
- Category
- Code Review & Quality
- First seen
- May 16, 2026