@autocode-cli/autocode 0.1.8 → 0.1.10

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 (67) hide show
  1. package/dist/cli/commands/new.d.ts.map +1 -1
  2. package/dist/cli/commands/new.js +20 -2
  3. package/dist/cli/commands/new.js.map +1 -1
  4. package/dist/server/api.js +1 -1
  5. package/dist/server/dashboard/pages/pipeline-configurator.d.ts.map +1 -1
  6. package/dist/server/dashboard/pages/pipeline-configurator.js +121 -4
  7. package/dist/server/dashboard/pages/pipeline-configurator.js.map +1 -1
  8. package/package.json +1 -1
  9. package/templates/catalog.yaml +3 -1
  10. package/templates/prompts/backlog.en.md +5 -2
  11. package/templates/prompts/backlog.fr.md +5 -2
  12. package/templates/prompts/changelog.en.md +5 -2
  13. package/templates/prompts/changelog.fr.md +5 -2
  14. package/templates/prompts/deploy-prod.en.md +5 -2
  15. package/templates/prompts/deploy-prod.fr.md +5 -2
  16. package/templates/prompts/deploy-staging.en.md +5 -2
  17. package/templates/prompts/deploy-staging.fr.md +5 -2
  18. package/templates/prompts/design.en.md +5 -2
  19. package/templates/prompts/design.fr.md +5 -2
  20. package/templates/prompts/dev.en.md +5 -2
  21. package/templates/prompts/dev.fr.md +5 -2
  22. package/templates/prompts/done.en.md +3 -1
  23. package/templates/prompts/done.fr.md +3 -1
  24. package/templates/prompts/git-commit.en.md +5 -2
  25. package/templates/prompts/git-commit.fr.md +5 -2
  26. package/templates/prompts/git-push.en.md +5 -2
  27. package/templates/prompts/git-push.fr.md +5 -2
  28. package/templates/prompts/git-tag.en.md +5 -2
  29. package/templates/prompts/git-tag.fr.md +5 -2
  30. package/templates/prompts/in-progress.en.md +5 -2
  31. package/templates/prompts/in-progress.fr.md +5 -2
  32. package/templates/prompts/qualification.en.md +5 -2
  33. package/templates/prompts/qualification.fr.md +5 -2
  34. package/templates/prompts/ready.en.md +5 -2
  35. package/templates/prompts/ready.fr.md +5 -2
  36. package/templates/prompts/retest-cypress.en.md +5 -2
  37. package/templates/prompts/retest-cypress.fr.md +5 -2
  38. package/templates/prompts/retest-playwright.en.md +5 -2
  39. package/templates/prompts/retest-playwright.fr.md +5 -2
  40. package/templates/prompts/retest.en.md +5 -2
  41. package/templates/prompts/retest.fr.md +5 -2
  42. package/templates/prompts/review-best-practices.en.md +5 -2
  43. package/templates/prompts/review-best-practices.fr.md +5 -2
  44. package/templates/prompts/review-code.en.md +5 -2
  45. package/templates/prompts/review-code.fr.md +5 -2
  46. package/templates/prompts/review-consistency.en.md +5 -2
  47. package/templates/prompts/review-consistency.fr.md +5 -2
  48. package/templates/prompts/review-no-duplication.en.md +5 -2
  49. package/templates/prompts/review-no-duplication.fr.md +5 -2
  50. package/templates/prompts/review-security.en.md +5 -2
  51. package/templates/prompts/review-security.fr.md +5 -2
  52. package/templates/prompts/specification.en.md +5 -2
  53. package/templates/prompts/specification.fr.md +5 -2
  54. package/templates/prompts/splitter.en.md +31 -0
  55. package/templates/prompts/splitter.fr.md +33 -0
  56. package/templates/prompts/testing-cypress.en.md +5 -2
  57. package/templates/prompts/testing-cypress.fr.md +5 -2
  58. package/templates/prompts/testing-integration.en.md +5 -2
  59. package/templates/prompts/testing-integration.fr.md +5 -2
  60. package/templates/prompts/testing-playwright.en.md +5 -2
  61. package/templates/prompts/testing-playwright.fr.md +5 -2
  62. package/templates/prompts/testing-unit.en.md +5 -2
  63. package/templates/prompts/testing-unit.fr.md +5 -2
  64. package/templates/prompts/update-docs.en.md +5 -2
  65. package/templates/prompts/update-docs.fr.md +5 -2
  66. package/templates/prompts/validate-staging.en.md +5 -2
  67. package/templates/prompts/validate-staging.fr.md +5 -2
package/templates/prompts/testing-integration.fr.md CHANGED
@@ -14,11 +14,14 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
14
14
  6. Tester les connexions aux services externes
15
15
  7. Corriger les tests en echec
16
16
  8. Commit + push des fichiers de test
17
- 9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
17
+ 9. Si travail hors scope detecte :
18
+ - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
19
+ - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
20
+ - Dans le scope : traiter directement dans le ticket actuel
18
21
  10. Documenter : `autocode comment <key> "Tests d'integration OK"`
19
22
  11. Avancer : `autocode next <key>`
20
23
 
21
- > Ou retour : `autocode move <key> <column>`
24
+ > Ou retour : `autocode move <key> <targetColumn>`
22
25
 
23
26
  ## Criteres de Validation
24
27
 
package/templates/prompts/testing-playwright.en.md CHANGED
@@ -12,11 +12,14 @@ Live functional testing with Playwright. Manually verify feature works by naviga
12
12
  4. Test edge cases
13
13
  5. Verify error handling
14
14
  6. Capture screenshots if needed
15
- 7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
15
+ 7. If out of scope work detected:
16
+ - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
17
+ - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
18
+ - In scope: handle directly in current ticket
16
19
  8. Document: `autocode comment <key> "Playwright tests OK"`
17
20
  9. Advance: `autocode next <key>`
18
21
 
19
- > Or return: `autocode move <key> <column>`
22
+ > Or return: `autocode move <key> <targetColumn>`
20
23
 
21
24
  ## Validation Criteria
22
25
 
package/templates/prompts/testing-playwright.fr.md CHANGED
@@ -12,11 +12,14 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
12
12
  4. Tester les cas limites
13
13
  5. Verifier la gestion d'erreurs
14
14
  6. Capturer des screenshots si necessaire
15
- 7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
15
+ 7. Si travail hors scope detecte :
16
+ - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
17
+ - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
18
+ - Dans le scope : traiter directement dans le ticket actuel
16
19
  8. Documenter : `autocode comment <key> "Tests Playwright OK"`
17
20
  9. Avancer : `autocode next <key>`
18
21
 
19
- > Ou retour : `autocode move <key> <column>`
22
+ > Ou retour : `autocode move <key> <targetColumn>`
20
23
 
21
24
  ## Criteres de Validation
22
25
 
package/templates/prompts/testing-unit.en.md CHANGED
@@ -14,11 +14,14 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
14
14
  6. Fix any failing tests
15
15
  7. Verify coverage meets project standards
16
16
  8. Commit + push test files
17
- 9. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
17
+ 9. If out of scope work detected:
18
+ - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
19
+ - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
20
+ - In scope: handle directly in current ticket
18
21
  10. Document: `autocode comment <key> "Unit tests passed: <coverage>%"`
19
22
  11. Advance: `autocode next <key>`
20
23
 
21
- > Or return: `autocode move <key> <column>`
24
+ > Or return: `autocode move <key> <targetColumn>`
22
25
 
23
26
  ## Validation Criteria
24
27
 
package/templates/prompts/testing-unit.fr.md CHANGED
@@ -14,11 +14,14 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
14
14
  6. Corriger les tests en echec
15
15
  7. Verifier que la couverture respecte les standards du projet
16
16
  8. Commit + push des fichiers de test
17
- 9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
17
+ 9. Si travail hors scope detecte :
18
+ - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
19
+ - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
20
+ - Dans le scope : traiter directement dans le ticket actuel
18
21
  10. Documenter : `autocode comment <key> "Tests unitaires OK : <couverture>%"`
19
22
  11. Avancer : `autocode next <key>`
20
23
 
21
- > Ou retour : `autocode move <key> <column>`
24
+ > Ou retour : `autocode move <key> <targetColumn>`
22
25
 
23
26
  ## Criteres de Validation
24
27
 
package/templates/prompts/update-docs.en.md CHANGED
@@ -12,11 +12,14 @@ Document changes for future developers and users.
12
12
  4. Update existing guides if impacted
13
13
  5. Verify doc consistency
14
14
  6. Commit + push
15
- 7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
15
+ 7. If out of scope work detected:
16
+ - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
17
+ - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
18
+ - In scope: handle directly in current ticket
16
19
  8. Document: `autocode comment <key> "Documentation updated"`
17
20
  9. Advance: `autocode next <key>`
18
21
 
19
- > Or return: `autocode move <key> <column>`
22
+ > Or return: `autocode move <key> <targetColumn>`
20
23
 
21
24
  ## Validation Criteria
22
25
 
package/templates/prompts/update-docs.fr.md CHANGED
@@ -12,11 +12,14 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
12
12
  4. Mettre a jour les guides existants si impactes
13
13
  5. Verifier la coherence de la doc
14
14
  6. Commit + push
15
- 7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
15
+ 7. Si travail hors scope detecte :
16
+ - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
17
+ - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
18
+ - Dans le scope : traiter directement dans le ticket actuel
16
19
  8. Documenter : `autocode comment <key> "Documentation mise a jour"`
17
20
  9. Avancer : `autocode next <key>`
18
21
 
19
- > Ou retour : `autocode move <key> <column>`
22
+ > Ou retour : `autocode move <key> <targetColumn>`
20
23
 
21
24
  ## Criteres de Validation
22
25
 
package/templates/prompts/validate-staging.en.md CHANGED
@@ -13,11 +13,14 @@ Final validation: verify everything works in staging AND git repo is clean.
13
13
  5. Verify visually everything is OK
14
14
  6. Capture proof (screenshot)
15
15
  7. Confirm feature works
16
- 8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
16
+ 8. If out of scope work detected:
17
+ - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
18
+ - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
19
+ - In scope: handle directly in current ticket
17
20
  9. Document: `autocode comment <key> "Staging validation OK"`
18
21
  10. Advance: `autocode next <key>`
19
22
 
20
- > Or return: `autocode move <key> <column>`
23
+ > Or return: `autocode move <key> <targetColumn>`
21
24
 
22
25
  ## Validation Criteria
23
26
 
package/templates/prompts/validate-staging.fr.md CHANGED
@@ -13,11 +13,14 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
13
13
  5. Verifier visuellement que tout est OK
14
14
  6. Capturer une preuve (screenshot)
15
15
  7. Confirmer que la feature fonctionne
16
- 8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
16
+ 8. Si travail hors scope detecte :
17
+ - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
18
+ - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
19
+ - Dans le scope : traiter directement dans le ticket actuel
17
20
  9. Documenter : `autocode comment <key> "Validation staging OK"`
18
21
  10. Avancer : `autocode next <key>`
19
22
 
20
- > Ou retour : `autocode move <key> <column>`
23
+ > Ou retour : `autocode move <key> <targetColumn>`
21
24
 
22
25
  ## Criteres de Validation
23
26