mirror of
https://github.com/CherryHQ/cherry-studio.git
synced 2026-07-07 07:03:00 +08:00
<!-- Template from https://github.com/kubevirt/kubevirt/blob/main/.github/PULL_REQUEST_TEMPLATE.md?--> <!-- Thanks for sending a pull request! Here are some tips for you: 1. Consider creating this PR as draft: https://github.com/CherryHQ/cherry-studio/blob/main/CONTRIBUTING.md --> ### What this PR does Before this PR: The PR checklist had no reminder for authors to self-review their code before requesting review. After this PR: A new "Self-review" checklist item reminds PR authors to review their own code using `/gh-pr-review`, `gh pr diff`, or the GitHub UI before requesting review from others. ### Why we need it and why it was done in this way Self-review catches obvious issues before reviewer time is spent, improving review efficiency. The following tradeoffs were made: N/A The following alternatives were considered: N/A Links to places where the discussion took place: N/A ### Breaking changes None ### Special notes for your reviewer The link to `/gh-pr-review` points to the skill definition at `/.claude/skills/gh-pr-review/SKILL.md`. ### Checklist This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list. - [x] PR: The PR description is expressive enough and will help future contributors - [x] Code: [Write code that humans can understand](https://en.wikiquote.org/wiki/Martin_Fowler#code-for-humans) and [Keep it simple](https://en.wikipedia.org/wiki/KISS_principle) - [x] Refactor: You have [left the code cleaner than you found it (Boy Scout Rule)](https://learning.oreilly.com/library/view/97-things-every/9780596809515/ch08.html) - [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required - [ ] Documentation: A [user-guide update](https://docs.cherry-ai.com) was considered and is present (link) or not required. Check this only when the PR introduces or changes a user-facing feature or behavior. - [x] Self-review: I have reviewed my own code (e.g., via [`/gh-pr-review`](/.claude/skills/gh-pr-review/SKILL.md), `gh pr diff`, or GitHub UI) before requesting review from others ### Release note ```release-note NONE ``` Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2.9 KiB
2.9 KiB
What this PR does
Before this PR:
After this PR:
Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Breaking changes
If this PR introduces breaking changes, please describe the changes and the impact on users.
Special notes for your reviewer
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.
- PR: The PR description is expressive enough and will help future contributors
- Code: Write code that humans can understand and Keep it simple
- Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
- Upgrade: Impact of this change on upgrade flows was considered and addressed if required
- Documentation: A user-guide update was considered and is present (link) or not required. Check this only when the PR introduces or changes a user-facing feature or behavior.
- Self-review: I have reviewed my own code (e.g., via
/gh-pr-review,gh pr diff, or GitHub UI) before requesting review from others
Release note