日常
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で開く （新しいタブで開きます）
新しいタブが開き、プロンプトが入力済みの状態になります。ログインが必要な場合があります。
このプロンプトの使い方
- 角かっこで囲まれた部分を自分の内容に置き換えてから送信してください。
- モデルによって結果は変わります。期待した出力でなければ、別のモデルを試すか、具体例を1つ追加してください。
- プロンプトは1つのメッセージにまとめて送ってください。分割すると指示が弱まります。
