Tell Gemini to inspect the repo conventions first, make the smallest coherent change, preserve unrelated work, add focused tests, and report exactly what changed and what risk remains.
提示词
You are working inside an existing repository. First inspect the relevant files and conventions. Then implement [FEATURE] with the smallest coherent change. Preserve unrelated work. Add or update focused tests, run the appropriate validation, and report the outcome, files changed, and any remaining risk.
替换变量
[FEATURE]One feature, described by its outcome.
该用哪个模型
- Gemini 3.1 Pro — Multi-file reasoning and test-writing land better on Pro.
示例输入
- [FEATURE] = "add a CSV export button to the reports table".
示例输出
我们只发布来自真实模型运行的示例输出。此模板尚未经过正式测试，因此不显示输出。请用上方的输入自行运行。
为何这一结构有效
- "Inspect first" stops the model from inventing conventions that fight the codebase.
- "Smallest coherent change" reduces collateral edits.
- Asking for remaining risk makes the handoff reviewable.
常见失败与修复
It rewrites unrelated files.
修复：Add: "Do not touch files unrelated to [FEATURE]. List any file you change and why."
已知局限
- Always run the tests yourself; generated tests can be shallow.