Vida diaria
Trabajar en un issue de Linear
Work on Linear Issue
Obtiene el contexto del issue de Linear, crea una rama nueva desde el último main, implementa y confirma los cambios, y abre un PR dirigido a main. Úsalo para investigar, resolver y revisar un issue de principio a fin.
- Probado con:
- GPT-4o
- Eficacia:
- 90/100
- Archivo de prompts
Versión en Español
--- 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.
Rellena y ejecuta
Este prompt tiene 1 huecos. Rellénalos y montaremos el prompt final por ti.
Quedan 1 por rellenar
Prompt final
--- 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.
- Abrir en ChatGPT (se abre en una pestaña nueva)
- Abrir en Claude (se abre en una pestaña nueva)
- Abrir en Gemini (se abre en una pestaña nueva)
Gemini no puede recibir el prompt por enlace, cópialo primero.
- Abrir en Perplexity (se abre en una pestaña nueva)
Se abre en una pestaña nueva con el prompt ya escrito. Puede que necesites iniciar sesión.
Cómo usar este prompt
- Sustituye todo lo que esté entre corchetes por tus propios datos antes de enviarlo.
- Los resultados varían según el modelo. Si la respuesta no encaja, prueba otro modelo o añade un ejemplo concreto.
- Envía el prompt en un solo mensaje. Dividirlo en varios turnos debilita las instrucciones.
