处理 Linear 工单

---
name: work-on-linear-issue
description: 你将收到一个 Linear 工单 ID，通常形式为 LLL-XX……其中 L 是字母，X 是数字。你的任务是在新分支上解决问题，并向 main 分支发起 PR。
---

你应该遵循以下步骤：

1. 使用 Linear MCP 获取工单的上下文信息，工单编号位于 $0。
2. 从 main 分支的最新版本开始，如有必要先执行 pull。然后创建一个新分支，格式为 claude/<ISSUE ID>-<工单的简短 3-4 个词描述>，并切换到该新分支。你所有的更改/提交都应在新分支上进行。
3. 根据工单信息对代码库进行研究，并制定一个实现计划。在规划过程中，如果遇到任何疑问，应提出澄清请求。每次验证步骤后都进入规划阶段。
4. 在实现过程中持续进行提交，遵循 Git 提交的最佳实践。
5. 当你认为工单已处理完毕后，以清晰、全新的视角重新审视你的更改，检查可能存在的问题、缺陷或边界情况。如果发现问题，应予以解决。
6. 当你确信已无问题、缺陷等成功实现更改后，向 main 分支创建 PR。

---
name: work-on-linear-issue
description: You will receive a Linear issue id usually on the the form of LLL-XX... where Ls are letters and Xs are digits. Your job is to resolve it on a new branch and open a PR to the branch main.
---

You should follow these steps:

1. Use the Linear MCP to get the context of the issue, the issue number is at $0.
2. Start on the latest version of main, do a pull if necesseray. Then create a new branch in the format of claude/<ISSUE ID>-<SHORT 3-4 WORD DESCRIPTION OF THE ISSUE> checkout to this new branch. All your changes/commits should happen on the new branch.
3. Do your research of the codebase with respect to the info of the issue and come up with an implementation plan. While planning if you have any confusions ask for clarifications. Enter to planning after every verification step.
4. Implement while commiting along the way, following git commit best practices.
5. After you think you are done with the issue, with a clear fresh new perspective, re-look at your changes to identify possible issues, bugs, or edge cases. If there is any address them.
6. After you are confident that you have implemented the changes without problems, bugs, etc. create a PR to the main branch.