optimize pr desc.

.gitee/PULL_REQUEST_TEMPLATE.en.md

@@ -6,11 +6,12 @@
 -->
 
 **What type of PR is this?**
-> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespaces from that line:
->
-> /kind bug
-> /kind task
-> /kind feature
+<!-- 
+Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. 
+
+If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`.
+-->
+/kind <label>
 
 
 **What does this PR do / why do we need it**:
@@ -23,6 +24,7 @@ Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
 -->
 Fixes #
 
+
 **Code review checklist [[illustration]](https://gitee.com/mindspore/community/blob/master/security/code_review_checklist_mechanism.md)**:
 
 - **Typical problems of security coding [[historical security coding cases reference]](https://gitee.com/mindspore/community/blob/master/security/security_coding_violation_cases.md)**

.gitee/PULL_REQUEST_TEMPLATE.zh-CN.md

@@ -6,11 +6,12 @@
 -->
 
 **What type of PR is this?**
-> Uncomment only one ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespaces from that line:
->
-> /kind bug
-> /kind task
-> /kind feature
+<!-- 
+Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. 
+
+If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`.
+-->
+/kind <label>
 
 
 **What does this PR do / why do we need it**:
@@ -23,6 +24,7 @@ Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
 -->
 Fixes #
 
+
 **Code review checklist [【代码检视checklist说明】](https://gitee.com/mindspore/community/blob/master/security/code_review_checklist_mechanism.md)**:
 
 - **典型安全编码问题 [【违反安全编码案例】](https://gitee.com/mindspore/community/blob/master/security/security_coding_violation_cases.md)**