일상
Linear 이슈 작업
Work on Linear Issue
Linear 이슈의 맥락을 확인하고, 최신 main에서 새 브랜치를 만들어 변경 사항을 구현한 뒤 커밋과 함께 main 대상 PR을 엽니다. 이슈를 코드베이스에서 해결하고 검토해야 할 때 사용합니다.
- 테스트 모델:
- 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에서 열기 (새 탭에서 열림)
새 탭이 열리고 프롬프트가 미리 입력됩니다. 서비스에 로그인되어 있어야 할 수 있습니다.
이 프롬프트 사용법
- 대괄호로 표시된 부분을 여러분의 내용으로 바꿔서 입력하세요.
- 모델에 따라 결과가 달라집니다. 원하는 답이 아니면 다른 모델을 쓰거나 구체적인 예시를 하나 덧붙이세요.
- 프롬프트는 한 번에 하나의 메시지로 보내세요. 여러 번에 나누면 지시가 약해집니다.
