菜单
代码重构 / 整理。任何重构必须先有覆盖待重构区域的测试网；分步原子 commit；每步 绿测，不允许"大爆炸式重构"。性能/行为变更属于 perf-flow / dev-flow，不在此范围。 Use when refactoring code, cleaning up tech debt, or restructuring without behavior change. Voice triggers: "重构", "整理代码", "/refactor-flow".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | refactor-flow |
| description | 代码重构 / 整理。任何重构必须先有覆盖待重构区域的测试网；分步原子 commit；每步 绿测，不允许"大爆炸式重构"。性能/行为变更属于 perf-flow / dev-flow，不在此范围。 Use when refactoring code, cleaning up tech debt, or restructuring without behavior change. Voice triggers: "重构", "整理代码", "/refactor-flow". |
| version | 0.1.0 |
| applies_to | ["all"] |
| priority | P1 |
| usage_frequency | weekly |
| depends_on | [] |
| related | ["test-driven-development","using-git-worktrees","testing-anti-patterns"] |
不改外部行为，只改内部结构（rename、提取函数、模块拆分、消除重复等）。
确认 _playbook.md Part B.3 启动参数；额外 refactor_target（要重构的模块/文件/目录）。
move_agent_to_root；建知识库目录（极简 META.md）。
/health 跑当前分数REFACTOR_BASELINE.md（行为基线 + 健康分基线）test(scope): 补充重构前覆盖测试prompt: "测试网就绪，重构方案如下：[方案 A 一句话摘要]。请确认："
options:
- "方案 OK，分步执行"
- "需要修改方案（说明）"
- "暂不重构（关闭流程）"
每步：
refactor(scope): 中文描述/qa（重点跑回归）/health 分数应持平或上升/review/ship → /land-and-deploy → /canary（监控同模块错误率，确认与基线一致）。
append _lessons.md：重构动因 + 收益（健康分变化）+ 成本（工时）。
/bugfix-flow 修复 + 上线，再回来继续META.md、REFACTOR_BASELINE.md、补测试 commit、若干原子重构 commit、/health 前后对比、PR 链接。
无。
/dev-flow 路由到（也可被用户直接触发）/bugfix-flow/perf-flow/qa、/health、/review/ship、/land-and-deploy、/canaryUse whenever an AI agent executes a multi-step task to save tokens, parallelize tool calls, cache prompts, and keep replies under 2000 chars
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Bug 修复全流程。强制 /investigate 找根因，禁止"看似修好就交付"。/freeze 锁定文件 防止顺手"清理"无关代码；先写复现失败测试再写修复。 Use when reporting bugs, errors, 500s, stack traces, or "it stopped working" type issues. Voice triggers: "修 bug", "/bugfix-flow", "bugfix".
开发组合拳总入口。根据输入形式（需求文档 / 原型项目 / 一句话）× 开发范围（前端 / 后端 / 全栈） × 修饰符（带设计稿 / 数据库迁移 / 只联调 等）自动路由到正确的子 skill。同时覆盖 4 类非需求任务： bugfix / 重构 / 性能优化 / 第三方接入。 Use when asked to "接需求", "开始开发", "/dev-flow", "组合拳", "dev flow", or whenever the user hands over a development task and you need to decide which workflow skill to invoke. Voice triggers: "接需求", "开始开发", "组合拳". Note: 阶段切片型 skills（/dev-understand、/dev-implement、/dev-ship-retro）按阶段拆分， 与本路由按场景类型拆分的子 skill 互补；当用户明确说"只做某阶段"时优先匹配那些 skill。
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
性能优化全流程。先 benchmark 立基线 → profile 找瓶颈 → 单一变量优化 → 再 benchmark 对比。禁止"凭感觉优化"，每个改动必须带数据证明。 Use when optimizing for performance, page speed, web vitals, or backend latency. Voice triggers: "性能优化", "/perf-flow", "提速".