@autocode-cli/autocode 0.1.10 → 0.1.12

package/templates/prompts/testing-cypress.fr.md

@@ -12,15 +12,14 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
 4. Decrire les tests clairement (describe/it)
 5. Executer les tests : npx cypress run
 6. Si echecs : corriger les tests ou le code
-7. Commit + push des tests
-8. Si travail hors scope detecte :
+7. Si travail hors scope detecte :
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Tests Cypress OK"`
-10. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Tests Cypress OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-integration.en.md

@@ -13,15 +13,14 @@ Run integration tests to verify components work correctly together. Ensure syste
 5. Test database operations
 6. Test external service connections
 7. Fix any failing tests
-8. Commit + push test files
-9. If out of scope work detected:
+8. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-10. Document: `autocode comment <key> "Integration tests passed"`
-11. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Integration tests passed"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-integration.fr.md

@@ -13,15 +13,14 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
 5. Tester les operations base de donnees
 6. Tester les connexions aux services externes
 7. Corriger les tests en echec
-8. Commit + push des fichiers de test
-9. Si travail hors scope detecte :
+8. Si travail hors scope detecte :
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-10. Documenter : `autocode comment <key> "Tests d'integration OK"`
-11. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Tests d'integration OK"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-playwright.en.md

@@ -16,10 +16,10 @@ Live functional testing with Playwright. Manually verify feature works by naviga
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Playwright tests OK"`
-9. Advance: `autocode next <key>`
+8. Document: `autocode comment <ticket-key> "Playwright tests OK"`
+9. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-playwright.fr.md

@@ -16,10 +16,10 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Tests Playwright OK"`
-9. Avancer : `autocode next <key>`
+8. Documenter : `autocode comment <ticket-key> "Tests Playwright OK"`
+9. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/testing-unit.en.md

@@ -13,15 +13,14 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
 5. Run all unit tests: `npm test` or equivalent
 6. Fix any failing tests
 7. Verify coverage meets project standards
-8. Commit + push test files
-9. If out of scope work detected:
+8. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-10. Document: `autocode comment <key> "Unit tests passed: <coverage>%"`
-11. Advance: `autocode next <key>`
+9. Document: `autocode comment <ticket-key> "Unit tests passed: <coverage>%"`
+10. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/testing-unit.fr.md

@@ -13,15 +13,14 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
 5. Executer tous les tests unitaires : `npm test` ou equivalent
 6. Corriger les tests en echec
 7. Verifier que la couverture respecte les standards du projet
-8. Commit + push des fichiers de test
-9. Si travail hors scope detecte :
+8. Si travail hors scope detecte :
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-10. Documenter : `autocode comment <key> "Tests unitaires OK : <couverture>%"`
-11. Avancer : `autocode next <key>`
+9. Documenter : `autocode comment <ticket-key> "Tests unitaires OK : <couverture>%"`
+10. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/update-docs.en.md

@@ -11,15 +11,14 @@ Document changes for future developers and users.
 3. Document new features
 4. Update existing guides if impacted
 5. Verify doc consistency
-6. Commit + push
-7. If out of scope work detected:
+6. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
    - In scope: handle directly in current ticket
-8. Document: `autocode comment <key> "Documentation updated"`
-9. Advance: `autocode next <key>`
+7. Document: `autocode comment <ticket-key> "Documentation updated"`
+8. Advance: `autocode next <ticket-key>`
 
-> Or return: `autocode move <key> <targetColumn>`
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/update-docs.fr.md

@@ -11,15 +11,14 @@ Documenter les changements pour les futurs developpeurs et utilisateurs.
 3. Documenter les nouvelles features
 4. Mettre a jour les guides existants si impactes
 5. Verifier la coherence de la doc
-6. Commit + push
-7. Si travail hors scope detecte :
+6. Si travail hors scope detecte :
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <key> "Documentation mise a jour"`
-9. Avancer : `autocode next <key>`
+7. Documenter : `autocode comment <ticket-key> "Documentation mise a jour"`
+8. Avancer : `autocode next <ticket-key>`
 
-> Ou retour : `autocode move <key> <targetColumn>`
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/validate-staging.en.md

@@ -7,20 +7,15 @@ Final validation: verify everything works in staging AND git repo is clean.
 ## Actions
 
 1. Execute git status - must be clean
-2. If uncommitted files: commit and push
-3. Navigate to staging environment
-4. Test developed feature
-5. Verify visually everything is OK
-6. Capture proof (screenshot)
-7. Confirm feature works
-8. If out of scope work detected:
-   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch -c ready`
-   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
-   - In scope: handle directly in current ticket
-9. Document: `autocode comment <key> "Staging validation OK"`
-10. Advance: `autocode next <key>`
-
-> Or return: `autocode move <key> <targetColumn>`
+2. Navigate to staging environment
+3. Test developed feature
+4. Verify visually everything is OK
+5. Capture proof (screenshot)
+6. Confirm feature works
+7. Document: `autocode comment <ticket-key> "Staging validation OK"`
+8. Advance: `autocode next <ticket-key>`
+
+> Or return: `autocode move <ticket-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/validate-staging.fr.md

@@ -7,20 +7,15 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
 ## Actions
 
 1. Executer git status - doit etre propre
-2. Si fichiers non commites : commit et push
-3. Naviguer vers l'environnement staging
-4. Tester la feature developpee
-5. Verifier visuellement que tout est OK
-6. Capturer une preuve (screenshot)
-7. Confirmer que la feature fonctionne
-8. Si travail hors scope detecte :
-   - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch -c ready`
-   - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
-   - Dans le scope : traiter directement dans le ticket actuel
-9. Documenter : `autocode comment <key> "Validation staging OK"`
-10. Avancer : `autocode next <key>`
-
-> Ou retour : `autocode move <key> <targetColumn>`
+2. Naviguer vers l'environnement staging
+3. Tester la feature developpee
+4. Verifier visuellement que tout est OK
+5. Capturer une preuve (screenshot)
+6. Confirmer que la feature fonctionne
+7. Documenter : `autocode comment <ticket-key> "Validation staging OK"`
+8. Avancer : `autocode next <ticket-key>`
+
+> Ou retour : `autocode move <ticket-key> <target-column-slug>`
 
 ## Criteres de Validation