Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
abhigyanpatwari avatar

Gitnexus Refactoring

  • 1.4k installs
  • 45.1k repo stars
  • Updated August 4, 2026
  • abhigyanpatwari/gitnexus

gitnexus-refactoring provides documented workflows for Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refac

About

The gitnexus-refactoring skill 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 impact target X direction upstream Map all dependents 2 query search_query X Find execution flows involving X 3 context name X See all incoming outgoing refs 4 Plan update order interfaces implementations callers tests If Index is stale run node gitnexus run cjs analyze in terminal Checklists Rename Symbol 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 rename dry_run false apply edits detect_changes verify only expected files changed Run tests for affected processes Extract Module context name target see all incoming outgoing refs impact target direction

  • "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

Gitnexus Refactoring by the numbers

  • 1,371 all-time installs (skills.sh)
  • +50 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #95 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

gitnexus-refactoring capabilities & compatibility

Capabilities
"rename this function safely" · "extract this into a module" · "split this service" · "move this to a new file" · any task involving renaming, extracting, splitti
Use cases
documentation
From the docs

What gitnexus-refactoring says it does

impact({target: "X", direction: "upstream"}) → Map all dependents 2.
SKILL.md
query({search_query: "X"}) → Find execution flows involving X 3.
SKILL.md
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-refactoring

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars45.1k
Security audit1 / 3 scanners passed
Last updatedAugust 4, 2026
Repositoryabhigyanpatwari/gitnexus

How do I use gitnexus-refactoring for the task described in its SKILL.md triggers?

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 sepa.

Who is it for?

Teams invoking gitnexus-refactoring when the user request matches documented triggers and prerequisites.

Skip if: Skip when cached docs are missing, the request is a negative trigger, or another sibling skill owns the workflow.

When should I use this skill?

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\"

What you get

Step-by-step guidance grounded in gitnexus-refactoring documentation and reference files.

  • Dependency impact map
  • Refactored code structure

Files

SKILL.mdMarkdownGitHub ↗

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. impact({target: "X", direction: "upstream"})  → Map all dependents
2. query({search_query: "X"})                            → Find execution flows involving X
3. context({name: "X"})                           → See all incoming/outgoing refs
4. Plan update order: interfaces → implementations → callers → tests
If "Index is stale" → run node .gitnexus/run.cjs analyze in terminal.

Checklists

Rename Symbol

- [ ] 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: rename({..., dry_run: false}) — apply edits
- [ ] detect_changes() — verify only expected files changed
- [ ] Run tests for affected processes

Extract Module

- [ ] context({name: target}) — see all incoming/outgoing refs
- [ ] impact({target, direction: "upstream"}) — find all external callers
- [ ] Define new module interface
- [ ] Extract code, update imports
- [ ] detect_changes() — verify affected scope
- [ ] Run tests for affected processes

Split Function/Service

- [ ] context({name: target}) — understand all callees
- [ ] Group callees by responsibility
- [ ] impact({target, direction: "upstream"}) — map callers to update
- [ ] Create new functions/services
- [ ] Update callers
- [ ] detect_changes() — verify affected scope
- [ ] Run tests for affected processes

Tools

rename — automated multi-file rename:

rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: true})
→ 12 edits across 8 files
→ 10 graph edits (high confidence), 2 ast_search edits (review)
→ Changes: [{file_path, edits: [{line, old_text, new_text, confidence}]}]

impact — map all dependents first:

impact({target: "validateUser", direction: "upstream"})
→ d=1: loginHandler, apiMiddleware, testUtils
→ Affected Processes: LoginFlow, TokenRefresh

detect_changes — verify your changes after refactoring:

detect_changes({scope: "all"})
→ Changed: 8 files, 12 symbols
→ Affected processes: LoginFlow, TokenRefresh
→ Risk: MEDIUM

cypher — custom reference queries:

MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "validateUser"})
RETURN caller.name, caller.filePath ORDER BY caller.filePath

Risk Rules

Risk FactorMitigation
Many callers (>5)Use rename for automated updates
Cross-area refsUse detect_changes after to verify scope
String/dynamic refsquery to find them
External/public APIVersion and deprecate properly

Example: Rename validateUser to authenticateUser

1. rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: true})
   → 12 edits: 10 graph (safe), 2 ast_search (review)
   → Files: validator.ts, login.ts, middleware.ts, config.json...

2. Review ast_search edits (config.json: dynamic reference!)

3. rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: false})
   → Applied 12 edits across 8 files

4. detect_changes({scope: "all"})
   → Affected: LoginFlow, TokenRefresh
   → Risk: MEDIUM — run tests for these flows

Related skills

Forks & variants (1)

Gitnexus Refactoring has 1 known copy in the catalog totaling 2 installs. They canonicalize to this original listing.

How it compares

Use gitnexus-refactoring for graph-backed safe restructuring rather than blind IDE rename or release tagging workflows.

FAQ

What does gitnexus-refactoring do?

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\"

When should I use 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\"

What are common prerequisites?

--- name: gitnexus-refactoring description: "Use when the user wants to rename, extract, split, move, or restructure code safely.

Is Gitnexus Refactoring safe to install?

skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.