How do I install the Refactoring skill?

Run npx skillmds@latest add tamnguyendinh/refactoring in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Refactoring skill do?

Use when the user asks to refactor code. It is listed under Coding & Dev Tools on SkillMD.

Is Refactoring safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Refactoring?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Refactoring free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Refactoring?

tamnguyendinh (@tamnguyendinh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Refactoring by tamnguyendinh — Agent Skill

Name: Refactoring
Author: tamnguyendinh

File contents

Refactoring With Anvien

Use this skill for behavior-preserving renames, extractions, moves, splits, and shared-code cleanup.

This skill is a workflow gate for refactoring work. It is not a command router. When a concrete Anvien command is needed, choose it directly from the generated Command Selection Guide.

Command Choices

Need	Use
Understand current ownership	MCP/CLI `context`; prefer `context file` or `context symbol` once target type is known
Check callers and flows before editing	MCP/CLI `impact --direction upstream`; prefer `impact file` or `impact symbol` once target type is known
Rename a symbol	MCP `rename` or CLI `anvien rename <symbol> <newName> --repo <repo>`
Check API route/contract consumers	MCP `api_impact` or CLI `anvien api impact [route] --repo <repo>`
Check route/tool blast radius	`anvien impact route <route> --repo <repo>` or `anvien impact tool <tool> --repo <repo>`
Verify changed scope before commit	MCP `detect_changes` or CLI `anvien detect-changes --repo <repo> --scope all`

Workflow

Refresh the graph with anvien analyze --force before graph-based refactoring.
Use context to inspect the exact target. If multiple candidates exist, use UID/file disambiguation.
Run upstream impact and report the blast radius. HIGH/CRITICAL means proceed carefully, not stop automatically.
For renames, start with a graph-guided dry run. Do not use find-and-replace for symbols.
Make behavior-preserving changes first. Defer unrelated cleanup unless required.
Run focused tests, broader tests when shared contracts are touched, and detect-changes.

Rename Flow

anvien rename oldName newName --repo <repo> --json
Inspect files, edit counts, graph edits, text-search edits, and ambiguity warnings.
Use --uid or --file if the dry run is ambiguous.
Apply with --apply only when the edit list matches the intended scope.

Extract, Split, Or Move Flow

Use context to identify callers/callees and nearby contracts.
Use impact to identify consumers that must remain compatible.
Move code in a small slice, update imports deliberately, and preserve behavior.
Re-run tests that cover affected flows and any API shape tests if contracts moved.

Current Limitations

Graph-guided rename is safer than text replacement, but generated files, dynamic references, string-based APIs, and external integrations still need source review and tests.

---name: refactoringdescription: Use when the user asks to refactor code.---# Refactoring With AnvienUse this skill for behavior-preserving renames, extractions, moves, splits, and shared-code cleanup.This skill is a workflow gate for refactoring work. It is not a command router. When a concrete Anvien command is needed, choose it directly from the generated Command Selection Guide.## Command Choices| Need | Use ||---|---|| Understand current ownership | MCP/CLI `context`; prefer `context file` or `context symbol` once target type is known || Check callers and flows before editing | MCP/CLI `impact --direction upstream`; prefer `impact file` or `impact symbol` once target type is known || Rename a symbol | MCP `rename` or CLI `anvien rename <symbol> <newName> --repo <repo>` || Check API route/contract consumers | MCP `api_impact` or CLI `anvien api impact [route] --repo <repo>` || Check route/tool blast radius | `anvien impact route <route> --repo <repo>` or `anvien impact tool <tool> --repo <repo>` || Verify changed scope before commit | MCP `detect_changes` or CLI `anvien detect-changes --repo <repo> --scope all` |## Workflow1. Refresh the graph with `anvien analyze --force` before graph-based refactoring.2. Use `context` to inspect the exact target. If multiple candidates exist, use UID/file disambiguation.3. Run upstream impact and report the blast radius. HIGH/CRITICAL means proceed carefully, not stop automatically.4. For renames, start with a graph-guided dry run. Do not use find-and-replace for symbols.5. Make behavior-preserving changes first. Defer unrelated cleanup unless required.6. Run focused tests, broader tests when shared contracts are touched, and `detect-changes`.## Rename Flow1. `anvien rename oldName newName --repo <repo> --json`2. Inspect files, edit counts, graph edits, text-search edits, and ambiguity warnings.3. Use `--uid` or `--file` if the dry run is ambiguous.4. Apply with `--apply` only when the edit list matches the intended scope.## Extract, Split, Or Move Flow- Use `context` to identify callers/callees and nearby contracts.- Use `impact` to identify consumers that must remain compatible.- Move code in a small slice, update imports deliberately, and preserve behavior.- Re-run tests that cover affected flows and any API shape tests if contracts moved.## Current LimitationsGraph-guided rename is safer than text replacement, but generated files, dynamic references, string-based APIs, and external integrations still need source review and tests.

Frequently asked questions

Refactoring