diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 4e4e2061b..90e3bcb47 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -5,6 +5,19 @@
 2. Ensure you have added or ran the appropriate tests and lint for your PR, please use `make lint` and `make test` before filing your PR, use `make clean` to tidy your go mod.
 3. If the PR is unfinished, you may need to mark it as a WIP(Work In Progress) PR or draft PR
 4. Please use a semantic commits format title, such as `<type>[optional scope]: <description>`, see: https://go-kratos.dev/docs/community/contribution#type
+5. at the same time, please note that similar work should be submitted in one PR as far as possible to reduce the workload of reviewers. Do not split a work into multiple PR unless it should.
+-->
+
+<!--
+🎉 感谢您向 Kratos 发送 PR 请求！以下是一些提示：
+如果这是你第一次为 Kratos 贡献，请阅读我们的贡献指南：https://go-kratos.dev/en/docs/community/contribution/
+2、确保您已经为您的 PR 添加或运行了适当的测试和lint，请在提交PR之前使用“make lint”和“make test”，使用“make clean”整理您的 go.mod。
+3、如果请购单未完成，您可能需要将其标记为 WIP（在制品）PR 或 draft PR
+4、请使用语义提交格式标题，如“<类型>[可选范围]：<说明>`，请参阅：https://go-kratos.dev/docs/community/contribution#type
+5. 同时请注意，同类的工作请尽量在一个PR中提交，以减轻 review 者的工作负担，不要把一项工作拆分成很多个PR，除非它应该这样做。
+-->
+
+<!--
 -->
 
 #### Description (what this PR does / why we need it):
@@ -26,4 +39,4 @@ Usage: `fixes/resolves #<issue number>`, or `fixes/resolves (paste link of issue
 <!--
 * Somethings that need extra attention for the reviewers
 * Some additional notes, TODO list, etc.
--->
\ No newline at end of file
+-->