Skip to content
Skills Library
Programming · Planning

refactor

/refactor

[UDS] 引導重構決策與策略選擇,包含「重構還是重寫」這個判斷。 Use when: 程式碼已經難以修改、在戰術性與架構性重構之間做選擇、要在老舊程式碼裡安全地動手。 Not for: 換到不同框架或主版本——請用 /migrate;清除除錯殘留與死碼——請用 /sweep。 Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債, 壞味道.

Licence
MIT
Last repository change
08.11.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

[UDS] 引導重構決策與策略選擇,包含「重構還是重寫」這個判斷。 Use when: 程式碼已經難以修改、在戰術性與架構性重構之間做選擇、要在老舊程式碼裡安全地動手。 Not for: 換到不同框架或主版本——請用 /migrate;清除除錯殘留與死碼——請用 /sweep。 Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債, 壞味道.

Arguments

/refactor [file or module | 檔案或模組]
Original author description

[UDS] 引導重構決策與策略選擇,包含「重構還是重寫」這個判斷。 Use when: 程式碼已經難以修改、在戰術性與架構性重構之間做選擇、要在老舊程式碼裡安全地動手。 Not for: 換到不同框架或主版本——請用 /migrate;清除除錯殘留與死碼——請用 /sweep。 Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債, 壞味道.

How it works

  1. 使用方式
  2. 策略快速參考
  3. 工作流程
  4. 使用範例
  5. 下一步引導
  6. 參考
  7. AI 代理行為
Original SKILL.md headings · 85 lines, 236 words
SKILL.md preview
---
name: refactor
source: ../../../../skills/refactoring-assistant/SKILL.md
source_version: 2.0.0
translation_version: 2.1.0
last_synced: 2026-10-12
source_hash: 22be2c4ae81e
status: current
scope: universal
description: |
  [UDS] 引導重構決策與策略選擇,包含「重構還是重寫」這個判斷。
  Use when: 程式碼已經難以修改、在戰術性與架構性重構之間做選擇、要在老舊程式碼裡安全地動手。
  Not for: 換到不同框架或主版本——請用 /migrate;清除除錯殘留與死碼——請用 /sweep。
  Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重構, 重寫, 技術債, 壞味道.
allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*), Bash(npx:*)
argument-hint: "[file or module | 檔案或模組]"
---

# 重構助手

> **語言**: [English](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/skills/refactoring-assistant/SKILL.md) | 繁體中文

引導重構決策、推薦策略,並提供逐步執行工作流程。

## 使用方式

| 命令 | 用途 |
|------|------|
| `/refactor` | 啟動互動式重構引導 |
| `/refactor decide` | 執行重構 vs 重寫決策樹 |
| `/refactor tactical` | 建議戰術性(日常)策略 |
| `/refactor strategic` | 引導戰略性/架構重構 |
| `/refactor legacy` | 遺留程式碼安全策略 |
| `/refactor debt` | 技術債評估 |

## 策略快速參考

### 戰術性策略(日常)

| 策略 | 使用時機 |
|------|---------|
| **準備式重構** | 新增被阻擋的功能之前 |
| **童子軍法則** | 任何維護工作中 |
| **紅-綠-重構** | TDD 開發循環 |

### 戰略性策略(架構)

| 策略 | 使用時機 |
|------|---------|
| **絞殺者無花果** | 逐步替換整個系統 |
| **防腐層** | 與遺留系統整合 |
| **抽象分支** | 在主幹上重構共享程式碼 |

### 安全防護策略(遺留程式碼)

| 策略 | 使用時機 |
|------|---------|
| **特徵化測試** | 任何遺留程式碼重構之前 |
| **草稿式重構** | 理解黑盒程式碼 |
| **尋找接縫** | 在遺留程式碼中注入測試替身 |

## 工作流程

1. **評估** - 識別要重構的程式碼,評估測試覆蓋率
2. **決策** - 需要時執行決策樹(重構 vs 重寫)
3. **選擇策略** - 根據範圍和風險選擇適當策略
4. **執行** - 遵循逐步工作流程,包含安全檢查
5. **驗證** - 執行測試以確認行為未被改變

## 使用範例

```
User: /refactor src/legacy-auth/
AI: Analyzing src/legacy-auth/...
    Test coverage: 23% — recommending safety-first approach.
    Suggested strategy: Characterization Tests + Preparatory Refactoring
```

```
User: /refactor decide
AI: Let me help you decide whether to refactor or rewrite.
    Question 1: Is the code currently working in production? [Y/N]
```

## 下一步引導

`/refactor` 完成後,AI 助手應建議:

> **重構完成。建議下一步:**
> - 執行 `/checkin` 通過品質關卡 ⭐ **推薦**
> - 執行 `/coverage` 確認重構後覆蓋率不下降
> - 執行 `/commit` 提交重構變更

## 參考

- 詳細指南:[guide.md](./guide.md)
- 核心規範:[refactoring-standards.md](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/core/refactoring-standards.md)

## AI 代理行為

> 完整的 AI 行為定義請參閱對應的命令文件:[`/refactor`](https://github.com/AsiaOstrich/universal-dev-standards/blob/main/skills/commands/refactor.md#ai-agent-behavior--ai-代理行為)
Files in this package (2)
  • SKILL.md 3 KB
  • guide.md 11 KB

Versions

RepositoryScoreLicence
This page · AsiaOstrich/universal-dev-standards95MIT
froglet-studio/cosmic-shore100MIT
mgiovani/cc-arsenal100MIT
jongio/skills100MIT
boshu2/agentops100Apache-2.0
y-miyazaki/terraform-aws-base100Apache-2.0
mickeyyaya/evolve-loop100Apache-2.0
j0hanz/j0hanz-marketplace100MIT
kriscard/kriscard-claude-plugins100MIT

Database snapshot: 13.11.2026 · package version 20734f39293d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 84refactoring-assistant
    [UDS] 引导重构决策与策略选择,包含「重构还是重写」这个判断。 Use when: 代码已经难以修改、在战术性与架构性重构之间做选择、要在老旧代码里安全地动手。 Not for: 换到不同框架或主版本——请用 /migrate;清除调试残留与死代码——请用 /sweep。 Keywords: refactor, rewrite, strangler, legacy code, technical debt, code smell, 重构, 重写, 技术债, 坏味道.
  • 90rewrite-vs-refactor
    Decide whether to refactor code in place or rewrite it from scratch using risk math, not frustration. Use when a component feels beyond repair and someone proposes starting over.
  • 91nightgauge-refactor-rewrite
    Refactor vs rewrite decision analysis engine. Evaluates brownfield codebases across 8 dimensions to produce data-driven recommendations with confidence levels, risk/benefit matrices, and hybrid approach suggestions. Use when deciding whether to refactor or rewrite a legacy…
  • 86refactoring
    Use when the user asks to refactor code.
  • 90refactoring-legacy
    Refactor and modernize legacy code safely: characterization tests, small reversible steps, strangler pattern, dead-code removal. Use when cleaning up, restructuring, migrating or paying down technical debt.
  • 90clean-room-rewrite
    Decide whether a legacy codebase should be rewritten or refactored, and when a rewrite wins, rebuild it clean-room — distill the old system into an executable behavior spec, have a builder that never reads the old source implement it, audit parity against the old code with…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.