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.
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.
Değişkenleri değiştirin
[FEATURE]One feature, described by its outcome.
Hangi model kullanılmalı
- Gemini 3.1 Pro — Multi-file reasoning and test-writing land better on Pro.
Örnek girdi
- [FEATURE] = "add a CSV export button to the reports table".
Örnek çıktı
Yalnızca gerçek model çalıştırmalarından elde edilen örnek çıktıları yayınlarız. Bu şablon henüz resmi olarak test edilmediğinden hiçbir çıktı gösterilmiyor. Yukarıdaki girdiyle kendiniz çalıştırın.
Bu yapı neden işe yarar
- "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.
Sık karşılaşılan hatalar ve düzeltmeler
It rewrites unrelated files.
Düzeltme: Add: "Do not touch files unrelated to [FEATURE]. List any file you change and why."
Bilinen sınırlamalar
- Always run the tests yourself; generated tests can be shallow.