From a4a17a607d3dd7af1afb323a7606d228b617bc4a Mon Sep 17 00:00:00 2001
From: SuperDragonXD <70206496+SuperDragonXD@users.noreply.github.com>
Date: Wed, 30 Jul 2025 12:50:25 +0800
Subject: [PATCH] chore(workflow): Introduce new PR template

---
 .github/pull_request_template.md | 43 ++++++++++++++++++++++++++------
 1 file changed, 35 insertions(+), 8 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 354827d6a7..7f1fb8b8a5 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,14 +1,41 @@
-## Description
+<!-- 
+  Thanks for your contribution! A clear description and a test plan are the best way to get your PR reviewed and merged quickly.
+  For simple `Style` or `Chore` changes, a detailed description is optional.
+-->
 
-<!-- Please include a summary of the change. Please also include relevant motivation and context. -->
+### Description
 
+<!-- A clear and concise one-paragraph summary of what this PR does. -->
 
 Fixes #(issue) <!-- optional -->
 
-## Type of change
-<!-- Replace :x: with :white_check_mark: to "check" the specified bullet -->
+### Reasoning
 
-:x: General change (non-breaking change that doesn't fit the below categories like copyediting)
-:x: Bug fix (non-breaking change which fixes an issue)
-:x: New feature (non-breaking change which adds functionality)
-:x: Breaking change (fix or feature that would cause existing functionality to not work as expected)
+<!-- 
+  (Optional - for major changes)
+  A more detailed explanation of the "why." 
+  - Why was this change necessary? (e.g., technical debt, user feedback, architectural improvement)
+  - What are the core principles of the new solution?
+-->
+
+
+### Testing
+
+<!-- 
+  (Optional - but highly encouraged for any functional change)
+  A step-by-step script for how to test these changes.
+-->
+
+
+### Type of change
+
+<!-- Please replace the :x: with a :white_check_mark: for the ONE line that best describes your change. -->
+
+:x: **Bug fix** (A non-breaking change that fixes an issue)
+:x: **New feature** (A non-breaking change that adds functionality)
+:x: **Breaking change** (A fix or feature that would cause existing functionality to not work as expected)
+:x: **Refactor** (A code change that neither fixes a bug nor adds a feature)
+:x: **Performance** (A code change that improves performance)
+:x: **Style** (Code style changes)
+:x: **Docs** (Changes to documentation)
+:x: **Chore** (Changes to the build process or other tooling)