Guides refactoring decisions with decision trees (refactor vs rewrite), recommends tactical/strategic/legacy strategies, and provides step-by-step workflows with safety checks and test verification.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-3 --plugin asiaostrich-universal-dev-standardsThis skill is limited to using the following tools:
Guide refactoring decisions, recommend strategies, and provide step-by-step execution workflows.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Guide refactoring decisions, recommend strategies, and provide step-by-step execution workflows.
引導重構決策、推薦策略，並提供逐步執行工作流程。
| Command | Purpose | 用途 |
|---|---|---|
/refactor | Start interactive refactoring guide | 啟動互動式重構引導 |
/refactor decide | Run refactor vs. rewrite decision tree | 執行重構 vs 重寫決策樹 |
/refactor tactical | Suggest tactical (daily) strategies | 建議戰術性（日常）策略 |
/refactor strategic | Guide strategic/architectural refactoring | 引導戰略性/架構重構 |
/refactor legacy | Legacy code safety strategies | 遺留程式碼安全策略 |
/refactor debt | Technical debt assessment | 技術債評估 |
| Strategy | When to Use | 使用時機 |
|---|---|---|
| Preparatory Refactoring | Before adding a blocked feature | 新增被阻擋的功能之前 |
| Boy Scout Rule | During any maintenance work | 任何維護工作中 |
| Red-Green-Refactor | TDD development cycle | TDD 開發循環 |
| Strategy | When to Use | 使用時機 |
|---|---|---|
| Strangler Fig | Replacing entire system gradually | 逐步替換整個系統 |
| Anti-Corruption Layer | Integrating with legacy system | 與遺留系統整合 |
| Branch by Abstraction | Shared code refactoring on trunk | 在主幹上重構共享程式碼 |
| Strategy | When to Use | 使用時機 |
|---|---|---|
| Characterization Tests | Before any legacy refactoring | 任何遺留程式碼重構之前 |
| Scratch Refactoring | Understanding black-box code | 理解黑盒程式碼 |
| Finding Seams | Injecting test doubles into legacy | 在遺留程式碼中注入測試替身 |
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]
After /refactor completes, the AI assistant should suggest:
重構完成。建議下一步 / Refactoring complete. Suggested next steps:
- 執行
/checkin通過品質關卡 ⭐ Recommended / 推薦 — Pass quality gates- 執行
/coverage確認重構後覆蓋率不下降 — Verify coverage not decreased- 執行
/commit提交重構變更 — Commit the refactoring changes
完整的 AI 行為定義請參閱對應的命令文件：
/refactorFor complete AI agent behavior definition, see the corresponding command file:
/refactor