日常生活
处理 Linear Issue
Work on Linear Issue
获取 Linear Issue 的上下文，从最新的 main 创建新分支并完成实现、提交代码，最后向 main 创建 PR。适用于需要从调查到复查完整解决一个 Issue 的场景。
- 测试模型:
- GPT-4o
- 有效性评分:
- 90/100
- 提示词归档
中文版本
--- 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.
填入内容并运行
这条提示词有 1 处待填。填好后我们会为你拼出完整提示词。
还有 1 处未填
完整提示词
--- 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.
- 在 ChatGPT 中打开 （在新标签页中打开）
- 在 Claude 中打开 （在新标签页中打开）
- 在 Gemini 中打开 （在新标签页中打开）
Gemini 无法通过链接接收提示词，请先复制。
- 在 Perplexity 中打开 （在新标签页中打开）
将在新标签页打开并已填入提示词。可能需要先登录该服务。
如何使用此提示词
- 发送前，请将方括号中的内容替换为你自己的信息。
- 不同模型的结果会有差异。若输出不理想，可换一个模型或补充一个具体示例。
- 请将提示词放在一条消息中发送。分多次发送会削弱指令效果。
