Feature/add pull request template

.github/PULL_REQUEST_TEMPLATE/feature.md

@@ -0,0 +1,41 @@
+> Please fill out the following sections to describe your pull request.
+
+## Summary of Changes
+<!-- Provide a brief summary of the changes you have made. -->
+
+## PR Type
+What kind of changes does this PR introduce? (Please check the relevant boxes and select the type.)
+
+- [ ] **Add**: Add a new feature
+- [ ] **Fix**: Fix a bug
+- [ ] **Style**: Change user UI design (CSS, etc.)
+- [ ] **Chore**: Changes that do not affect the code (typo fixes, tab size changes, variable name changes)
+- [ ] **Refactor**: Code refactoring
+- [ ] **Docs**: Add or modify comments and documentation
+- [ ] **Test**: Add or refactor tests
+- [ ] **Build**: Modify build-related configurations or package managers
+- [ ] **Rename**: Rename files or folders
+- [ ] **Remove**: Delete files or folders
+
+## Detailed Description of Changes
+<!-- Describe the changes in detail. You can break this down into multiple sections if necessary. -->
+
+## Related Issues
+<!-- List related issue numbers. For example: #123 -->
+
+## Screenshots (if applicable)
+<!-- Attach screenshots if there are UI changes. -->
+
+## PR Checklist
+Ensure your PR meets the following requirements:
+
+- [ ] The commit messages follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) convention.
+  - Example: `Add: New user login feature`, `Fix: Payment error bug`
+- [ ] Tests for the changes have been added or updated.
+- [ ] Documentation has been updated accordingly.
+- [ ] All necessary changes for code review are included.
+- [ ] The build passes successfully.
+- [ ] A deployment plan has been established if necessary.
+
+## Additional Notes
+<!-- Include any additional information or context that might be helpful for reviewers. -->