Remove Debug Backdoors Before Release
Added 2026-10
Remove Debug Backdoors Before Release — Chinese original prompt
请检查 [项目] 里为了联调方便加的临时通道：万能验证码、固定令牌、跳过鉴权的开关、返回详细错误的调试模式、可直接执行的运维接口。逐项确认是否在生产环境可达，并给出关闭或加环境限制的改法。输出：排查清单与命中情况、每项的风险等级、修改方式、防止再次上线的检查手段。
Site original
Chinese original
Example
Sample input
上线前检查项目里的临时通道：万能验证码、跳过鉴权开关、返回详细错误的调试模式。
The output should include
- 逐项确认生产环境是否可达
- 给关闭或加环境限制的改法
- 给防止再次上线的检查手段
Replace these placeholders 1
Swap the bracketed parts for your own details before sending.
[项目]
How to use
用配置开关关掉不够，代码里留着入口迟早会被重新打开。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.