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周前更新