gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"
Best for Large codebasesWorks with GitHubLow risk
⌘source
- author
@abhigyanpatwari- language
- TypeScript
★28kstars
3.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Renames symbols safely across the codebase
- ·Extracts code into separate modules
- ·Moves code to new files
- ·Splits services or components
- ·Analyzes dependencies before making changes
- ·Provides previews of changes before applying
Use Cases
- →Renaming a function that's used in multiple files
- →Extracting a reusable utility into its own module
- →Splitting a large service class into smaller focused classes
- →Moving a component to a new directory structure
- →Restructuring code to improve maintainability
Best for
- ✓Large codebases
- ✓Team projects
- ✓Legacy code modernization
Not ideal for
- !One-off script modifications
- !Simple find-and-replace operations
FAQs
name
gitnexus-refactoring
description
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
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
Workflow
1. gitnexus_impact({target: "X", direction: "upstream"}) → Map all dependents
2. gitnexus_query({query: "X"}) → Find execution flows involving X
3. gitnexus_context({name: "X"}) → See all incoming/outgoing refs
4. Plan update order: interfaces → implementations → callers → tests
If "Index is stale" → run
npx gitnexus analyzein terminal.
Checklists
Rename Symbol
- [ ] gitnexus_rename({symbol_name: "oldName", new_name: "newName", dry_run: true}) — preview all edits
- [ ] Review graph edits (high confidence) and ast_search edits (review carefully)
- [ ] If satisfied: gitnexus_rename({..., dry_run: false}) — apply edits
- [ ] gitnexus_detect_changes() — verify only expected files changed
- [ ] Run tests for affected processes
Extract Module
- [ ] gitnexus_context({name: target}) — see all incoming/outgoing refs
$install
1-click copynpx skills add abhigyanpatwari/GitNexus --skill gitnexus-refactoringSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.