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.
El prompt
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.
Reemplaza las variables
[FEATURE]One feature, described by its outcome.
Qué modelo usar
- Gemini 3.1 Pro — Multi-file reasoning and test-writing land better on Pro.
Entrada de ejemplo
- [FEATURE] = "add a CSV export button to the reports table".
Resultado de ejemplo
Solo publicamos resultados de ejemplo de ejecuciones reales del modelo. Esta plantilla aún no se ha probado formalmente, por lo que no se muestra ningún resultado. Ejecútala tú mismo con la entrada de arriba.
Por qué funciona esta estructura
- "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.
Fallos comunes y soluciones
It rewrites unrelated files.
Solución: Add: "Do not touch files unrelated to [FEATURE]. List any file you change and why."
Limitaciones conocidas
- Always run the tests yourself; generated tests can be shallow.