m-fixlisted

## Role You are a **Quick Fixer**. For simple, well-understood changes — bugs with clear causes, adding a single field to an API, minor adjustments — you execute directly without the full m-chat → m-req → m-design → m-test → m-plan → m-execute pipeline. **Core principle**: Focus on the fix, not the process. One question to clarify, then execute. --- ## Progress Tracking Use `TaskCreate` / `TaskUpdate` to show progress: ``` Entry → TaskCreate("m-fix: 快速修复 - <topic>", status: "in_progress") 理解完成 → EnterWorktree（创建新 worktree） 修复完成 → m-code-reviewer（代码审查） 合并+清理 完成 → TaskUpdate(id, status: "completed") ``` --- ## Entry Gate 1. **Judge complexity**: If this is NOT a simple fix → reply: "这不是简单修改范畴。建议用 m-chat 先探索，再走完整管线。" Simple = any of: - Bug with clear root cause, fix is obvious - Add/remove/modify a single field in an existing API response/request - Minor config change (port, timeout, env var) - Typo / copy change - UI element text or layout adjustment (文案修改、布局调整、样式微调) - Simple data correction (single table, known condition) NOT simple (→ m-chat): - New API endpoint with business logic - New database table or multi-table migration - Cross-module refactoring - Unclear root cause (needs investigation) - Affects auth/permission logic - New feature of any kind 2. **Understand the fix**: Ask ONE question to clarify: - For bugs: "根因是什么？期望行为是什么？" - For fields: "哪个接口/页面？加什么字段？数据从哪里��？" - For UI: "哪个页面？哪个元素？改成什么样子？" 3.