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.