La versión breve
- Un buen prompt de programación describe el comportamiento actual, el cambio que se busca y cómo se comprobará el resultado. Dale al asistente una parte pequeña del repositorio y pide un diff que puedas probar.
- No pegues credenciales, datos privados de clientes ni repositorios propietarios completos en un asistente no autorizado. Ejecuta los comandos y las pruebas en tu propio entorno. Que un parche parezca correcto no demuestra que funcione.
Un buen prompt de programación describe el comportamiento actual, el cambio que se busca y cómo se comprobará el resultado. Dale al asistente una parte pequeña del repositorio y pide un diff que puedas probar.
No pegues credenciales, datos privados de clientes ni repositorios propietarios completos en un asistente no autorizado. Ejecuta los comandos y las pruebas en tu propio entorno. Que un parche parezca correcto no demuestra que funcione.
Cómo usar esta colección
Elige la tarea más parecida a tu trabajo. Copia el prompt, sustituye la escena o el contexto de código genérico por tus datos y conserva las restricciones que te permitan evaluar el resultado. Cambia una variable cada vez para saber qué ha mejorado.
El método sigue la guía de ingeniería de prompts de GitHub Copilot: aporta contexto concreto y revisa el resultado, sin dar por correcta una primera respuesta bien presentada.
Prompts de diagnóstico
Este grupo se centra en el diagnóstico. Facilita tu código y el comando de pruebas antes de aceptar la respuesta.
1. Un analizador de fechas que falla
Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
2. Una consulta lenta a la base de datos
Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
3. Un formulario que se envía dos veces
Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
4. Una API con errores incoherentes
Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
5. Un caso límite de paginación
Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
6. Una prueba de integración inestable
Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
7. Un límite de subida de archivos
Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
8. Un error al invalidar la caché
Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
9. Un bucle de reintentos en una cola
Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
10. Una comprobación de autorización
Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then state competing hypotheses, request a minimal reproduction and identify evidence that separates them. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta la reproducción propuesta antes de aplicar un parche.
Prompts de implementación
Este grupo se centra en la implementación. Facilita tu código y el comando de pruebas antes de aceptar la respuesta.
11. Un analizador de fechas que falla
Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
12. Una consulta lenta a la base de datos
Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
13. Un formulario que se envía dos veces
Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
14. Una API con errores incoherentes
Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
15. Un caso límite de paginación
Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
16. Una prueba de integración inestable
Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
17. Un límite de subida de archivos
Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
18. Un error al invalidar la caché
Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
19. Un bucle de reintentos en una cola
Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
20. Una comprobación de autorización
Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then make the smallest change that satisfies the stated behavior and show a focused diff. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Revisa el diff para detectar cambios ajenos a la tarea y accesos a datos no previstos.
Prompts para probar casos límite
Este grupo se centra en probar los casos límite. Facilita tu código y el comando de pruebas antes de aceptar la respuesta.
21. Un analizador de fechas que falla
Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
22. Una consulta lenta a la base de datos
Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
23. Un formulario que se envía dos veces
Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
24. Una API con errores incoherentes
Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
25. Un caso límite de paginación
Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
26. Una prueba de integración inestable
Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
27. Un límite de subida de archivos
Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
28. Un error al invalidar la caché
Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
29. Un bucle de reintentos en una cola
Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
30. Una comprobación de autorización
Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then add unit or integration cases for empty, invalid and concurrent inputs as appropriate. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Ejecuta las pruebas y, cuando sea posible, comprueba que fallen antes de aplicar la corrección.
Prompts para revisar la seguridad
Este grupo se centra en revisar la seguridad. Facilita tu código y el comando de pruebas antes de aceptar la respuesta.
31. Un analizador de fechas que falla
Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
32. Una consulta lenta a la base de datos
Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
33. Un formulario que se envía dos veces
Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
34. Una API con errores incoherentes
Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
35. Un caso límite de paginación
Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
36. Una prueba de integración inestable
Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
37. Un límite de subida de archivos
Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
38. Un error al invalidar la caché
Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
39. Un bucle de reintentos en una cola
Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
40. Una comprobación de autorización
Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then inspect authorization, input validation, error disclosure and rollback behavior. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Contrasta las afirmaciones sobre seguridad con las rutas y las políticas de la base de datos.
Prompts para documentar la entrega
Este grupo se centra en documentar la entrega. Facilita tu código y el comando de pruebas antes de aceptar la respuesta.
41. Un analizador de fechas que falla
Help with a failing date parser in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
42. Una consulta lenta a la base de datos
Help with a slow database query in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
43. Un formulario que se envía dos veces
Help with a form with duplicate submissions in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
44. Una API con errores incoherentes
Help with an API with inconsistent errors in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
45. Un caso límite de paginación
Help with a pagination edge case in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
46. Una prueba de integración inestable
Help with a flaky integration test in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
47. Un límite de subida de archivos
Help with a file upload limit in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
48. Un error al invalidar la caché
Help with a cache invalidation bug in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
49. Un bucle de reintentos en una cola
Help with a queue retry loop in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
50. Una comprobación de autorización
Help with an authorization check in my existing codebase. Ask for the relevant file, expected behavior, actual behavior and test command if I have not supplied them. Then write a concise changelog, usage example and rollback note tied to the implementation. Preserve public interfaces unless evidence requires a change. Show assumptions, a focused diff and the exact command I should run. Do not invent files, test results or security guarantees.Revisión: Elimina las afirmaciones que no se hayan medido ni probado.
Qué comprobar antes de usar el resultado
No pegues credenciales, datos privados de clientes ni repositorios propietarios completos en un asistente no autorizado. Ejecuta los comandos y las pruebas en tu propio entorno. Que un parche parezca correcto no demuestra que funcione.
Si el resultado no resuelve la tarea, acorta el prompt y especifica el dato o la restricción que falta. Guarda la versión utilizada para poder reproducir el recurso final o el cambio de código.
Para seguir leyendo
¿Tienes una pregunta o una corrección?
Contactar con Thrive
