메뉴
Bug 修复全流程。强制 /investigate 找根因，禁止"看似修好就交付"。/freeze 锁定文件 防止顺手"清理"无关代码；先写复现失败测试再写修复。 Use when reporting bugs, errors, 500s, stack traces, or "it stopped working" type issues. Voice triggers: "修 bug", "/bugfix-flow", "bugfix".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use 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
开发组合拳总入口。根据输入形式（需求文档 / 原型项目 / 一句话）× 开发范围（前端 / 后端 / 全栈） × 修饰符（带设计稿 / 数据库迁移 / 只联调 等）自动路由到正确的子 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", "提速".
代码重构 / 整理。任何重构必须先有覆盖待重构区域的测试网；分步原子 commit；每步 绿测，不允许"大爆炸式重构"。性能/行为变更属于 perf-flow / dev-flow，不在此范围。 Use when refactoring code, cleaning up tech debt, or restructuring without behavior change. Voice triggers: "重构", "整理代码", "/refactor-flow".
| name | bugfix-flow |
| description | Bug 修复全流程。强制 /investigate 找根因，禁止"看似修好就交付"。/freeze 锁定文件 防止顺手"清理"无关代码；先写复现失败测试再写修复。 Use when reporting bugs, errors, 500s, stack traces, or "it stopped working" type issues. Voice triggers: "修 bug", "/bugfix-flow", "bugfix". |
| version | 0.1.0 |
| applies_to | ["all"] |
| priority | P1 |
| usage_frequency | weekly |
| depends_on | ["systematic-debugging"] |
| related | ["root-cause-tracing","test-driven-development","verification-before-completion"] |
线上/线下报告的 Bug、错误、栈追踪、"以前能用现在不行"。
确认 _playbook.md Part B.3 启动参数；额外需要 bug_report（用户描述 / 截图 / 日志）。
move_agent_to_root；建知识库目录（极简 META.md）；如有 _lessons.md 加载；用 /learn 检索"曾经修过类似问题"。
prompt: "请提供 Bug 信息（可全选）："
options:
- "已粘贴报错堆栈/日志"
- "已提供复现步骤"
- "已提供截图/录屏"
- "需要我用 cursor-ide-browser 自己复现"
allow_multiple: true
把现象写入 BUG_REPORT.md：环境 / 步骤 / 实际 vs 预期 / 频率。
/investigate）/investigate 走完 4 阶段（investigate/analyze/hypothesize/implement）RCA.md（模板见 _playbook.md Part E.10）prompt: "根因已确认（RCA.md），修复方案有几种："
options:
- "用方案 A（推荐）"
- "用方案 B（备选，更保守）"
- "需要更多调查（说明）"
git checkout -b fix/[short-slug]test(scope): 复现 [bug 摘要]/freeze 锁定相关目录，避免"顺手清理"无关代码fix(scope): 修复 [bug 摘要]/unfreeze/qa quick + /reviewIMPACT_ANALYSIS.md 列出的回归点/cso 若涉及鉴权/数据可见性/ship（PR 描述带 RCA.md 链接）→ /land-and-deploy → /canary。
append _lessons.md：根因类型 / 怎么发现的 / 怎么避免再次发生。
/investigate 或升级请求帮助META.md、BUG_REPORT.md、RCA.md、复现失败测试 commit、修复 commit、/qa 报告、PR 链接。
无标准修饰符；可叠加 M4（如修复涉及数据修复脚本）→ 必须在 RCA.md 加"数据修复说明 + 回滚方案"。
/dev-flow 路由到（也可被用户直接触发）/investigate/qa、/review、/cso/ship、/land-and-deploy、/canary