<!--
如果您正在寻求帮助，请先在我们的讨论区中进行交流。
If you're looking for help, please check our Discussions section first.

我们鼓励使用英文，如果不能直接使用，可以使用翻译软件，您仍旧可以保留中文原文。
Please try to use English to describe your issue, or at least provide a snippet of English translation.

请不要在没有创建 Issue 的情况下创建 Pull Request。
Please do not create a Pull Request without creating an issue first.

微小的变更（如错别字修复）不需要创建 Issue。
Trivial changes like typos do not require a Github issue.

提交 PR 之前请务必先阅读我们的贡献指南。
Please read our Contributing Guide(CONTRIBUTING.md) before submitting your Pull Request.

⚠️ 注意 / Note：

不要重复创建类似的 PR，当你发现需要调整一个 PR 的时候，优先选择编辑修改它，而不是关闭之后再创建一个。
Do not create a Pull Request without creating an issue first.
-->

## 🔗 相关问题 / Related Issue

<!-- 请先创建 Issue 讨论，然后在这里链接 -->
<!-- Please create an issue for discussion first, then link it here -->

**Issue 链接 / Issue Link:** <mark>#{$IssueNumber}</mark> 👈👈

<!-- 请修改 {$IssueNumber} 为真实的编号。 -->
<!-- Please update {$IssueNumber} to an actual number. -->

- [ ] 我已经创建了相关 Issue 并进行了讨论 / I have created and discussed the related issue
- [ ] 这是一个微小的修改（如错别字），不需要 Issue / This is a trivial change (like typo fix) that doesn't need an issue

## 📋 变更类型 / Type of Change

- [ ] 🐛 Bug 修复 / Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ 新功能 / New feature (non-breaking change which adds functionality)
- [ ] 💥 破坏性变更 / Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] 📚 文档更新 / Documentation update
- [ ] 🔧 重构 / Refactoring (no functional changes)
- [ ] ⚡ 性能优化 / Performance improvement
- [ ] 📦 依赖升级 / Dependency upgrade (update dependencies to newer versions)
- [ ] 🚀 功能增强 / Feature enhancement (improve existing functionality without breaking changes)
- [ ] 🧹 代码清理 / Code cleanup

## 📝 变更目的 / Purpose of the Change

<!-- 详细描述这个变更的目的和必要性 -->
<!-- Detailed description of the purpose and necessity of this change -->

## 📋 主要变更 / Brief Changelog

<!-- 列出主要的变更内容 -->
<!-- List the main changes -->

-
-
-

## 🧪 验证变更 / Verifying this Change

<!-- 描述如何验证这个变更是正确的 -->
<!-- Describe how to verify that this change is correct -->

### 测试步骤 / Test Steps

1.
2.
3.

### 测试覆盖 / Test Coverage

- [ ] 我已经添加了单元测试 / I have added unit tests
- [ ] 所有现有测试都通过 / All existing tests pass
- [ ] 我已经进行了手动测试 / I have performed manual testing

## 📸 截图 / Screenshots

<!-- 如果适用，请添加截图来展示变更效果 -->
<!-- If applicable, add screenshots to demonstrate the changes -->

## ✅ 贡献者检查清单 / Contributor Checklist

请确保你的 Pull Request 符合以下要求 / Please ensure your Pull Request meets the following requirements:

**基本要求 / Basic Requirements:**

- [ ] 确保有 GitHub Issue 对应这个变更（微小变更如错别字除外）/ Make sure there is a Github issue filed for the change (trivial changes like typos excluded)
- [ ] 你的 Pull Request 只解决一个 Issue，没有包含其他不相关的变更 / Your PR addresses just this issue, without pulling in other changes - one PR resolves one issue
- [ ] PR 中的每个 commit 都有有意义的主题行和描述 / Each commit in the PR has a meaningful subject line and body

**代码质量 / Code Quality:**

- [ ] 我的代码遵循项目的代码规范 / My code follows the project's coding standards
- [ ] 我已经进行了自我代码审查 / I have performed a self-review of my code
- [ ] 我已经为复杂的代码添加了必要的注释 / I have commented my code, particularly in hard-to-understand areas

**测试要求 / Testing Requirements:**

- [ ] 我已经编写了必要的单元测试来验证逻辑正确性 / I have written necessary unit-tests to verify the logic correction
- [ ] 当存在跨模块依赖时，我尽量使用了 mock / I have used mocks when cross-module dependencies exist
- [ ] 代码检查通过 / Lint checks pass
- [ ] 单元测试通过 / Unit tests pass

**文档和兼容性 / Documentation and Compatibility:**

- [ ] 我已经更新了相应的文档 / I have made corresponding changes to the documentation
- [ ] 如果有破坏性变更，我已经在 PR 描述中详细说明 / If there are breaking changes, I have documented them in detail
- [ ] 我已经考虑了向后兼容性 / I have considered backward compatibility

## 📋 附加信息 / Additional Notes

<!-- 任何其他相关信息，如已知问题、后续计划等 -->
<!-- Any other relevant information, such as known issues, future plans, etc. -->

---

**审查者注意事项 / Reviewer Notes:**

<!-- 为审查者提供的特殊说明或需要重点关注的地方 -->
<!-- Special instructions for reviewers or areas that need special attention -->
