Refactor

作者 parcadeid07ff4b06b62無授權條款3.9K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫8 個月前更新

Code refactoring workflow - analyze → plan → implement → review → validate

僅含說明Software Development
AI 產生的概覽

指導五階段程式碼重構流程：分析、規劃、實作、審查與驗證。

功能
此技能定義了一套分階段的重構工作流程，依序進行分析、規劃、實作、審查與驗證，並將每個階段指派給指定的代理。它會產出分析報告、逐步重構計畫、程式碼變更、審查報告與測試報告。它也列出重構原則、常見重構類型，以及 dry-run、step-by-step 等安全選項。
適用情境
當被要求重構程式碼、清理程式碼、將邏輯抽取成模組、調整程式庫結構或減少技術債時使用。它適合需要先規劃、再審查並依測試驗證的較大規模重構工作。
執行需求
不包含指令碼，僅為指示。它假定執行環境中的代理能呼叫指定的子代理，並執行測試、型別檢查與程式碼檢查。

/refactor - Refactoring Workflow

Safe refactoring with review gates.

When to Use

  • "Refactor X"
  • "Clean up this code"
  • "Extract this into a module"
  • "Improve the architecture of Y"
  • Large-scale code restructuring
  • Technical debt reduction

Workflow Overview

┌──────────┐    ┌────────────┐    ┌──────────┐    ┌──────────┐    ┌───────────┐│ phoenix  │───▶│   plan-    │───▶│  kraken  │───▶│plan-reviewer│───▶│ arbiter  ││          │    │   agent    │    │          │    │          │    │           │└──────────┘    └────────────┘    └──────────┘    └──────────┘    └───────────┘  Analyze         Plan             Implement       Review          Verify  current         changes          refactor        changes         tests pass

Agent Sequence

#AgentRoleOutput
1phoenixAnalyze current code, identify improvement areasAnalysis report
2plan-agentCreate safe refactoring planStep-by-step plan
3krakenImplement the refactoringCode changes
4plan-reviewerReview changes for correctnessReview report
5arbiterVerify all tests still passTest report

Refactoring Principles

  1. Tests first: Ensure adequate test coverage before refactoring
  2. Small steps: Each change should be independently verifiable
  3. Behavior preserved: No functional changes during refactor
  4. Reviewable: Changes should be easy to review

Execution

Phase 1: Analyze

Task(  subagent_type="phoenix",  prompt="""  Analyze for refactoring: [TARGET_CODE]
  Identify:  - Current pain points  - Code smells  - Improvement opportunities  - Risk areas  - Test coverage gaps  """)

Phase 2: Plan

Task(  subagent_type="plan-agent",  prompt="""  Plan refactoring: [TARGET_CODE]
  Analysis: [from phoenix]
  Create:  - Step-by-step refactoring plan  - Each step should be:    - Small and focused    - Independently testable    - Reversible  - Identify files affected  - Risk mitigation strategy  """)

Phase 3: Implement

Task(  subagent_type="kraken",  prompt="""  Implement refactoring: [TARGET_CODE]
  Plan: [from plan-agent]
  Requirements:  - Follow plan exactly  - Run tests after each step  - Stop if tests fail  - NO behavior changes  """)

Phase 4: Review

Task(  subagent_type="plan-reviewer",  prompt="""  Review refactoring: [TARGET_CODE]
  Changes: [git diff from kraken]
  Check:  - Behavior preserved  - No unintended changes  - Code quality improved  - Patterns consistent  """)

Phase 5: Validate

Task(  subagent_type="arbiter",  prompt="""  Validate refactoring: [TARGET_CODE]
  - Run full test suite  - Verify no regressions  - Check type errors  - Run linting  """)

Refactoring Types

Extract Module

phoenix → plan-agent → kraken → plan-reviewer → arbiter

Rename/Restructure

phoenix → kraken → arbiter  (simpler, skip detailed planning)

Architecture Change

phoenix → plan-agent → [kraken → plan-reviewer] × N phases → arbiter

Example

User: /refactor Extract the validation logic into a separate module
Claude: Starting /refactor workflow...
Phase 1: Analyzing current structure...[Spawns phoenix]Found: Validation logic spread across 4 files- form.ts (lines 45-120)- api.ts (lines 200-280)- user.ts (lines 15-45)- order.ts (lines 88-130)
Phase 2: Planning extraction...[Spawns plan-agent]Plan:1. Create src/validation/index.ts2. Extract common validators3. Update imports one file at a time4. Run tests after each change
Phase 3: Implementing...[Spawns kraken]Completed all 4 steps, tests green after each
Phase 4: Reviewing changes...[Spawns plan-reviewer]✅ All behavior preserved✅ DRY improved (removed 45 duplicate lines)✅ New structure consistent
Phase 5: Final validation...[Spawns arbiter]✅ 312 tests passing, 0 regressions
Refactoring complete!

Safety Flags

  • --dry-run: Plan but don't implement
  • --step-by-step: Pause after each change for approval
  • --coverage-check: Require >80% coverage before proceeding

來源與署名

來源：parcadei/continuous-claude-v3位於.claude/skills/refactor提交d07ff4b

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 parcadei/continuous-claude-v3 的技能

Tldr Stats

parcadei

顯示工作階段 token 用量、API 費用、TLDR 壓縮節省金額與 hook 活動的儀表板。

Data & Analytics3.9K8 個月前更新

Wiring

parcadei

指導驗證已建置的基礎設施元件是否真的被呼叫，而非成為死程式碼。

Software Development3.9K8 個月前更新

Workflow Router

parcadei

將使用者的目標路由到對應的專家代理與資源層級，用於研究、規劃、建置或修復任務。

AI & Agents3.9K8 個月前更新

Validate Agent

parcadei

依據當前最佳實務驗證技術方案中的技術選型，並產出驗證交接文件。

Software Development3.9K8 個月前更新

Tour

parcadei

當使用者詢問能力時，提供友善的入門導覽，概述代理能做什麼。

AI & Agents3.9K8 個月前更新

Tldr Overview

parcadei

使用 TLDR 工具鏈產生節省 token 的專案概覽，涵蓋檔案樹、程式結構、呼叫圖與複雜度。

Software Development3.9K8 個月前更新

更多Software Development技能

Playground

anthropics

精選

建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。

Software Development37K今天更新

M5 Onboard

anthropics

精選

透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。

Software Development37K今天更新

Cardputer Buddy

anthropics

精選

指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精選

依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。

Software Development32K5 週前更新

Vercel React Native Skills

vercel-labs

精選

React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。

Software Development32K5 週前更新

Vercel React Best Practices

vercel-labs

精選

Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。

Software Development32K5 週前更新