Official agent skill

Gitnexus Refactoring

by aws-samples in aws-samples/sample-kolya-br-proxy

A skill your agent uses when the user wants to rename, extract, split, move, or restructure code safely.

OfficialMIT-0Auto-check passedDevelopment

Install Gitnexus Refactoring

skills CLI
$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-refactoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-refactoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-refactoring .claude/skills/gitnexus-refactoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gitnexus-refactoring
GitHub stars
106
Used in
11 other repos
Token cost
~1k tokens
SKILL.md length
109 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT-0

At a glance

A skill your agent uses when the user wants to rename, extract, split, move, or restructure code safely.

  • The user wants to rename
  • SKILL.md covers When to Use, Workflow, Checklists and Tools, plus 2 more sections
  • Calls npx
  • Restructure code safely

What it does

Gitnexus Refactoring is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. 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"

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. The licence is MIT-0.

When your agent uses it

  • The user wants to rename
  • Restructure code safely

Example prompts

  • “Rename this function”
  • “Extract this into a module”
  • “Refactor this class”
  • “/gitnexus-refactoring”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 9c3dcee. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gitnexus Refactoring loads about 1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 109 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws-samples/sample-kolya-br-proxy at commit 9c3dcee, republished under its MIT-0 licence (© aws-samples). 109 words, ~1,010 tokens.

Download SKILL.mdSave it as .claude/skills/gitnexus-refactoring/SKILL.md (or your agent's skills folder).
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 analyze in 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
- [ ] gitnexus_impact({target, direction: "upstream"}) — find all external callers
- [ ] Define new module interface
- [ ] Extract code, update imports
- [ ] gitnexus_detect_changes() — verify affected scope
- [ ] Run tests for affected processes
Split Function/Service
- [ ] gitnexus_context({name: target}) — understand all callees
- [ ] Group callees by responsibility
- [ ] gitnexus_impact({target, direction: "upstream"}) — map callers to update
- [ ] Create new functions/services
- [ ] Update callers
- [ ] gitnexus_detect_changes() — verify affected scope
- [ ] Run tests for affected processes

Tools

gitnexus_rename — automated multi-file rename:

gitnexus_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}]}]

gitnexus_impact — map all dependents first:

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

gitnexus_detect_changes — verify your changes after refactoring:

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

gitnexus_cypher — custom reference queries:

cypher
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 gitnexus_rename for automated updates
Cross-area refsUse detect_changes after to verify scope
String/dynamic refsgitnexus_query to find them
External/public APIVersion and deprecate properly

Example: Rename validateUser to authenticateUser

1. gitnexus_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. gitnexus_rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: false})
   → Applied 12 edits across 8 files

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

© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/gitnexus/gitnexus-refactoring of aws-samples/sample-kolya-br-proxy.

Open the folder on GitHubat commit 9c3dcee

Used in 12 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in aws-samples/sample-kolya-br-proxy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gitnexus Refactoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gitnexus Refactoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gitnexus Refactoring this skillaws-samples/sample-kolya-br-proxy10611 repos~1kAutomated safety check: PassMIT-0
Guidelinesakash-network/node1.1k22 repos~577Automated safety check: PassMIT
Component Refactoringlangflow-ai/langflow156k—~3.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed
  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed

More from aws-samples/sample-kolya-br-proxy

  • Gitnexus Debugging

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user is debugging a bug, tracing an error, or asking why something fails.

    106 GitHub starsUsed in 11 repos~780 tokens
    Auto-check passed
  • Gitnexus Exploring

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.

    106 GitHub starsUsed in 11 repos~749 tokens
    Auto-check passed
  • Gitnexus Impact Analysis

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code.

    106 GitHub starsUsed in 11 repos~723 tokens
    Auto-check passed
  • Gitnexus CLI

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos.

    106 GitHub starsUsed in 10 repos~822 tokens
    Auto-check passed
  • Gitnexus Guide

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference.

    106 GitHub starsUsed in 10 repos~867 tokens
    Auto-check passed

Categories

Questions about Gitnexus Refactoring

What does Gitnexus Refactoring do?

A skill your agent uses when the user wants to rename, extract, split, move, or restructure code safely. Gitnexus Refactoring is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user wants to rename, extract, split, move, or restructure code safely.

When should I use Gitnexus Refactoring?

Gitnexus Refactoring fits situations like: the user wants to rename; restructure code safely.

How do I install Gitnexus Refactoring in Claude Code?

Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-refactoring -a claude-code`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-refactoring in aws-samples/sample-kolya-br-proxy) into .claude/skills/gitnexus-refactoring in your project. Claude Code loads it when a task matches its description.

How do I install Gitnexus Refactoring in Codex?

Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-refactoring -a codex`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-refactoring in aws-samples/sample-kolya-br-proxy) into .agents/skills/gitnexus-refactoring in your project. Codex loads it when a task matches its description.

Can I use Gitnexus Refactoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-refactoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitnexus-refactoring, .gemini/skills/gitnexus-refactoring, .github/skills/gitnexus-refactoring and .opencode/skills/gitnexus-refactoring in your project.

What does Gitnexus Refactoring need to run?

Going by SKILL.md and its folder, Gitnexus Refactoring needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Gitnexus Refactoring access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gitnexus Refactoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gitnexus Refactoring use?

Gitnexus Refactoring is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gitnexus Refactoring use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gitnexus Refactoring?

Skills that share tags, products or a category with Gitnexus Refactoring: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and ast-grep Structural Search (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gitnexus Refactoring?

aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-kolya-br-proxy, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.

Source: aws-samples/sample-kolya-br-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.