fix-it-never-work-around-it
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseFix It, Never Work Around It
修复问题，而非规避问题
Critical Rules
核心规则
🚨 Rule 1: Follow the prescribed process exactly. If a step in the process fails, fix the root cause. Never skip, replace, or approximate the step. If you don't fix it, the problem recurs and all subsequent work is compromised. This does not apply to expected failures like TDD red phase — a failing test is the process working correctly.
Example: The code review subagent failed. ❌ "I'll review my own code and push." ✅ Fix why the subagent failed.
🚨 Rule 2: Follow instructions exactly. If a tool or command doesn't produce the expected result and there is no obvious alternative that produces the exact same result, stop immediately. Fix the root cause or ask for help. Never fabricate, approximate, or substitute.
Example: API authentication failed. ❌ "I'll define some likely values instead." ✅ Fix the authentication or ask the user.
🚨 规则1：严格遵循既定流程。 如果流程中的某一步失败，修复其根本原因。绝不要跳过、替换或简化该步骤。如果不修复问题，它会再次出现，后续所有工作都会受到影响。这不适用于预期内的失败，比如TDD的红阶段——测试失败是流程正常运行的表现。
示例：代码审查子Agent失败。❌ "我自己审查代码然后推送。" ✅ 修复子Agent失败的原因。
🚨 规则2：严格遵循指令。 如果工具或命令未产生预期结果，且没有明显的替代方案能产生完全相同的结果，请立即停止。修复根本原因或寻求帮助。绝不要编造、简化或替换内容。
示例：API认证失败。❌ "我来定义一些可能的值替代。" ✅ 修复认证问题或向用户求助。
Workaround Detection
规避行为检测
If you catch yourself using any of these phrases, you are about to workaround. STOP.
| Workaround Signal | What You're Actually Doing |
|---|---|
| "Let me check via X directly" | Bypassing the broken tool |
| "X is broken, let me use Y instead" | Abandoning the fix |
| "Let me try a different approach" | Avoiding the actual problem |
| "I'll work around this by..." | Literally saying it |
| "Alternatively, we can..." | Proposing a bypass |
| "Since X isn't working, let me..." | Giving up on fixing X |
| "Let me just manually..." | Bypassing automation |
| "I'll skip this step and..." | Ignoring the failure |
| "Let me fall back to..." | Retreating from the fix |
如果你发现自己使用以下任一表述，说明你即将采取规避行为。立即停止。
| 规避信号 | 你的实际行为 |
|---|---|
| "Let me check via X directly" | 绕过故障工具 |
| "X is broken, let me use Y instead" | 放弃修复 |
| "Let me try a different approach" | 回避实际问题 |
| "I'll work around this by..." | 明确表示要规避 |
| "Alternatively, we can..." | 提议绕过方案 |
| "Since X isn't working, let me..." | 放弃修复X |
| "Let me just manually..." | 绕过自动化流程 |
| "I'll skip this step and..." | 忽略故障 |
| "Let me fall back to..." | 放弃修复尝试 |
Anti-patterns
反模式
❌ The Helpful Bypass
❌ 看似有用的绕过
⏺ Bash(npm run build)
⎿ Error: Module not found '@company/shared'
⏺ The build has a dependency issue. Let me check the
source files directly to understand the code structure.The build is broken. Reading source files "directly" doesn't fix the build.
⏺ Bash(npm run build)
⎿ Error: Module not found '@company/shared'
⏺ The build has a dependency issue. Let me check the
source files directly to understand the code structure.构建失败了。直接阅读源文件并不能修复构建问题。
❌ The Tool Swap
❌ 工具替换
⏺ Bash(nx show projects)
⎿ Error: Failed to process project graph
⏺ NX project graph is broken. Let me check the tasks
via gh directly and read the PRD.The NX project graph is broken. Using doesn't fix the project graph. Every NX command will fail until this is fixed.
gh⏺ Bash(nx show projects)
⎿ Error: Failed to process project graph
⏺ NX project graph is broken. Let me check the tasks
via gh directly and read the PRD.NX项目图已损坏。使用并不能修复项目图。在修复之前，所有NX命令都会失败。
ghMandatory Checklist
强制检查清单
When a command or process fails unexpectedly:
- Verify you have STOPPED your current task
- Verify you are investigating the ROOT CAUSE of the failure
- Verify your proposed fix makes the ORIGINAL command/process work
- Verify you are NOT using a different tool/source/approach to bypass
- Verify the original command succeeds after your fix
Do not resume your previous task until all checks pass.
🚨 REMEMBER: Following the process and following instructions is MORE important than achieving a result by any means necessary. Consistency and reliability are crucial. Do not improvise, do not try to be helpful when the process cannot be followed.
当命令或流程意外失败时：
- 确认你已停止当前任务
- 确认你正在调查失败的根本原因
- 确认你提出的修复方案能让原命令/流程正常运行
- 确认你没有使用其他工具/来源/方法进行绕过
- 确认修复后原命令执行成功
在所有检查项通过之前，不要恢复之前的任务。
🚨 谨记：遵循流程和指令比不择手段达成结果更重要。一致性和可靠性至关重要。不要即兴发挥，当流程无法遵循时，不要试图‘帮忙’。