@autocode-cli/autocode 0.1.12 → 0.1.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (77) hide show
  1. package/README.md +1 -1
  2. package/dist/cli/commands/init.js +1 -1
  3. package/dist/cli/commands/init.js.map +1 -1
  4. package/dist/cli/commands/list.js +2 -2
  5. package/dist/cli/commands/list.js.map +1 -1
  6. package/dist/cli/commands/move.js +3 -3
  7. package/dist/cli/commands/move.js.map +1 -1
  8. package/dist/cli/commands/new.js +3 -3
  9. package/dist/cli/commands/new.js.map +1 -1
  10. package/dist/core/column.d.ts +0 -4
  11. package/dist/core/column.d.ts.map +1 -1
  12. package/dist/core/column.js +0 -6
  13. package/dist/core/column.js.map +1 -1
  14. package/dist/core/ticket.d.ts +1 -1
  15. package/dist/core/ticket.js +4 -4
  16. package/dist/core/ticket.js.map +1 -1
  17. package/dist/core/workflow.d.ts +1 -1
  18. package/dist/core/workflow.js +4 -4
  19. package/dist/server/api.d.ts.map +1 -1
  20. package/dist/server/api.js +73 -4
  21. package/dist/server/api.js.map +1 -1
  22. package/dist/server/dashboard/pages/pipeline-configurator.d.ts.map +1 -1
  23. package/dist/server/dashboard/pages/pipeline-configurator.js +176 -0
  24. package/dist/server/dashboard/pages/pipeline-configurator.js.map +1 -1
  25. package/dist/server/dashboard/scripts/index.js +3 -3
  26. package/dist/services/claude.d.ts +4 -1
  27. package/dist/services/claude.d.ts.map +1 -1
  28. package/dist/services/claude.js +7 -4
  29. package/dist/services/claude.js.map +1 -1
  30. package/package.json +1 -1
  31. package/templates/analysis-prompt.en.md +77 -0
  32. package/templates/analysis-prompt.fr.md +87 -0
  33. package/templates/catalog.yaml +1 -1
  34. package/templates/prompts/backlog.en.md +8 -19
  35. package/templates/prompts/backlog.fr.md +8 -19
  36. package/templates/prompts/design.en.md +2 -2
  37. package/templates/prompts/design.fr.md +2 -2
  38. package/templates/prompts/dev.en.md +2 -2
  39. package/templates/prompts/dev.fr.md +2 -2
  40. package/templates/prompts/done.en.md +2 -2
  41. package/templates/prompts/done.fr.md +2 -2
  42. package/templates/prompts/in-progress.en.md +2 -2
  43. package/templates/prompts/in-progress.fr.md +2 -2
  44. package/templates/prompts/qualification.en.md +2 -2
  45. package/templates/prompts/qualification.fr.md +2 -2
  46. package/templates/prompts/retest-cypress.en.md +2 -6
  47. package/templates/prompts/retest-cypress.fr.md +2 -6
  48. package/templates/prompts/retest-playwright.en.md +1 -4
  49. package/templates/prompts/retest-playwright.fr.md +1 -4
  50. package/templates/prompts/retest.en.md +1 -4
  51. package/templates/prompts/retest.fr.md +1 -4
  52. package/templates/prompts/review-best-practices.en.md +2 -6
  53. package/templates/prompts/review-best-practices.fr.md +2 -6
  54. package/templates/prompts/review-code.en.md +2 -6
  55. package/templates/prompts/review-code.fr.md +2 -6
  56. package/templates/prompts/review-consistency.en.md +2 -6
  57. package/templates/prompts/review-consistency.fr.md +2 -6
  58. package/templates/prompts/review-no-duplication.en.md +2 -6
  59. package/templates/prompts/review-no-duplication.fr.md +2 -6
  60. package/templates/prompts/review-security.en.md +2 -2
  61. package/templates/prompts/review-security.fr.md +2 -2
  62. package/templates/prompts/specification.en.md +2 -2
  63. package/templates/prompts/specification.fr.md +2 -2
  64. package/templates/prompts/splitter.en.md +3 -4
  65. package/templates/prompts/splitter.fr.md +3 -4
  66. package/templates/prompts/testing-cypress.en.md +1 -4
  67. package/templates/prompts/testing-cypress.fr.md +1 -4
  68. package/templates/prompts/testing-integration.en.md +1 -4
  69. package/templates/prompts/testing-integration.fr.md +1 -4
  70. package/templates/prompts/testing-playwright.en.md +1 -4
  71. package/templates/prompts/testing-playwright.fr.md +1 -4
  72. package/templates/prompts/testing-unit.en.md +1 -4
  73. package/templates/prompts/testing-unit.fr.md +1 -4
  74. package/templates/prompts/update-docs.en.md +2 -6
  75. package/templates/prompts/update-docs.fr.md +2 -6
  76. package/templates/prompts/ready.en.md +0 -31
  77. package/templates/prompts/ready.fr.md +0 -31
package/templates/prompts/update-docs.en.md CHANGED
@@ -11,12 +11,8 @@ Document changes for future developers and users.
11
11
  3. Document new features
12
12
  4. Update existing guides if impacted
13
13
  5. Verify doc consistency
14
- 6. If out of scope work detected:
15
- - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
16
- - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
17
- - In scope: handle directly in current ticket
18
- 7. Document: `autocode comment <ticket-key> "Documentation updated"`
19
- 8. Advance: `autocode next <ticket-key>`
14
+ 6. Document: `autocode comment <ticket-key> "Documentation updated"`
15
+ 7. Advance: `autocode next <ticket-key>`
20
16
 
21
17
  > Or return: `autocode move <ticket-key> <target-column-slug>`
22
18
 
package/templates/prompts/update-docs.fr.md CHANGED
@@ -11,12 +11,8 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
11
11
  3. Documenter les nouvelles features
12
12
  4. Mettre a jour les guides existants si impactes
13
13
  5. Verifier la coherence de la doc
14
- 6. Si travail hors scope detecte :
15
- - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
16
- - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
17
- - Dans le scope : traiter directement dans le ticket actuel
18
- 7. Documenter : `autocode comment <ticket-key> "Documentation mise a jour"`
19
- 8. Avancer : `autocode next <ticket-key>`
14
+ 6. Documenter : `autocode comment <ticket-key> "Documentation mise a jour"`
15
+ 7. Avancer : `autocode next <ticket-key>`
20
16
 
21
17
  > Ou retour : `autocode move <ticket-key> <target-column-slug>`
22
18
 
package/templates/prompts/ready.en.md DELETED
@@ -1,31 +0,0 @@
1
- # Ready
2
-
3
- ## Role
4
-
5
- Qualified tickets ready to be worked on. All information needed is available.
6
-
7
- ## Actions
8
-
9
- 1. Analyze ticket and acceptance criteria
10
- 2. Explore codebase to understand existing context
11
- 3. Plan modifications (files to create/modify)
12
- 4. Implement the solution
13
- 5. Test locally that it works
14
- 6. If out of scope work detected:
15
- - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
16
- - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
17
- - In scope: handle directly in current ticket
18
- 7. Document: `autocode comment <ticket-key> "Work completed"`
19
- 8. Advance: `autocode next <ticket-key>`
20
-
21
- > Or return: `autocode move <ticket-key> <target-column-slug>`
22
-
23
- ## Validation Criteria
24
-
25
- - [ ] Feature/fix is implemented
26
- - [ ] Local tests pass
27
- - [ ] A comment summarizes work done
28
-
29
- ## Notes
30
-
31
- For investigation: documented answer is the deliverable. For bug: identify root cause before coding fix.
package/templates/prompts/ready.fr.md DELETED
@@ -1,31 +0,0 @@
1
- # Ready
2
-
3
- ## Role
4
-
5
- Tickets qualifies prets a etre travailles. Toutes les informations necessaires sont disponibles.
6
-
7
- ## Actions
8
-
9
- 1. Analyser le ticket et les criteres d'acceptation
10
- 2. Explorer le codebase pour comprendre le contexte existant
11
- 3. Planifier les modifications (fichiers a creer/modifier)
12
- 4. Implementer la solution
13
- 5. Tester localement que ca fonctionne
14
- 6. Si travail hors scope detecte :
15
- - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
16
- - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
17
- - Dans le scope : traiter directement dans le ticket actuel
18
- 7. Documenter : `autocode comment <ticket-key> "Travail effectue"`
19
- 8. Avancer : `autocode next <ticket-key>`
20
-
21
- > Ou retour : `autocode move <ticket-key> <target-column-slug>`
22
-
23
- ## Criteres de Validation
24
-
25
- - [ ] Feature/fix implementee
26
- - [ ] Tests locaux passent
27
- - [ ] Un commentaire resume le travail effectue
28
-
29
- ## Notes
30
-
31
- Pour investigation : la reponse documentee est le livrable. Pour bug : identifier la cause racine avant de coder le fix.