Agent Skills › tintinweb/pi-gitnexus › gitnexus-refactoring

gitnexus-refactoring

GitHub

用于安全地重命名、提取、拆分或移动代码的重构技能。通过GitNexus分析依赖和影响范围，提供预演与验证步骤，确保重构过程的安全性与准确性。

skills/gitnexus-refactoring/SKILL.md tintinweb/pi-gitnexus

Trigger Scenarios

用户要求安全地重命名函数或符号用户需要将代码提取为新模块用户希望拆分服务或函数用户需要移动代码到不同文件

Install

npx skills add tintinweb/pi-gitnexus --skill gitnexus-refactoring -g -y

More Options

Use without installing

npx skills use tintinweb/pi-gitnexus@gitnexus-refactoring

指定 Agent (Claude Code)

npx skills add tintinweb/pi-gitnexus --skill gitnexus-refactoring -a claude-code -g -y

安装 repo 全部 skill

npx skills add tintinweb/pi-gitnexus --all -g -y

预览 repo 内 skill

npx skills add tintinweb/pi-gitnexus --list

SKILL.md

Frontmatter

{
    "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 /gitnexus analyze to rebuild.

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

Risk Rules

Risk Factor	Mitigation
Many callers (>5)	Use gitnexus_rename for automated updates
Cross-area refs	Use detect_changes after to verify scope
String/dynamic refs	gitnexus_query to find them
External/public API	Version 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)

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