@autocode-cli/autocode 0.1.4 → 0.1.6

package/templates/prompts/qualification.en.md

@@ -0,0 +1,30 @@
+# Qualification
+
+## Role
+
+Analyze and qualify the ticket requirement. Ensure the request is clear, feasible, and properly scoped.
+
+## Actions
+
+1. Read the ticket description and acceptance criteria
+2. Identify ambiguities or missing information
+3. Assess technical feasibility
+4. Estimate complexity (simple/medium/complex)
+5. Identify dependencies with other tickets or systems
+6. If clarification needed: add comment with questions
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+8. Document: `autocode comment <key> "Qualification complete: <summary>"`
+9. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Requirement is clear and unambiguous
+- [ ] Acceptance criteria are testable
+- [ ] Technical approach identified
+- [ ] No blocking dependencies
+
+## Notes
+
+A well-qualified ticket saves development time. When in doubt, ask for clarification rather than assuming.

package/templates/prompts/qualification.fr.md

@@ -0,0 +1,30 @@
+# Qualification
+
+## Role
+
+Analyser et qualifier le besoin du ticket. S'assurer que la demande est claire, faisable et correctement delimitee.
+
+## Actions
+
+1. Lire la description du ticket et les criteres d'acceptation
+2. Identifier les ambiguites ou informations manquantes
+3. Evaluer la faisabilite technique
+4. Estimer la complexite (simple/moyenne/complexe)
+5. Identifier les dependances avec d'autres tickets ou systemes
+6. Si clarification necessaire : ajouter un commentaire avec les questions
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+8. Documenter : `autocode comment <key> "Qualification terminee : <resume>"`
+9. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Le besoin est clair et sans ambiguite
+- [ ] Les criteres d'acceptation sont testables
+- [ ] L'approche technique est identifiee
+- [ ] Pas de dependances bloquantes
+
+## Notes
+
+Un ticket bien qualifie fait gagner du temps en developpement. En cas de doute, demander des clarifications plutot que supposer.

package/templates/{columns/01_ready.en.md → prompts/ready.en.md}

@@ -12,7 +12,7 @@ Qualified tickets ready to be worked on. All information needed is available.
 4. Implement the solution
 5. Test locally that it works
 6. Commit + push work done
-7. If out of scope work detected: `autocode new <title> <description>`
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 8. Document: `autocode comment <key> "Work completed"`
 9. Advance: `autocode next <key>`
 

package/templates/{columns/01_ready.fr.md → prompts/ready.fr.md}

@@ -12,7 +12,7 @@ Tickets qualifies prets a etre travailles. Toutes les informations necessaires s
 4. Implementer la solution
 5. Tester localement que ca fonctionne
 6. Commit + push du travail effectue
-7. Si travail hors scope detecte : `autocode new <title> <description>`
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 8. Documenter : `autocode comment <key> "Travail effectue"`
 9. Avancer : `autocode next <key>`
 

package/templates/prompts/retest-cypress.en.md

@@ -0,0 +1,29 @@
+# Retest Cypress
+
+## Role
+
+Re-run all automated E2E tests to ensure refactoring did not introduce regressions.
+
+## Actions
+
+1. Run full Cypress test suite: npx cypress run
+2. Compare results with pre-refactoring run
+3. If new failures: identify cause (test or code issue)
+4. Fix any regressions before proceeding
+5. Commit test fixes if needed
+6. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+7. Document: `autocode comment <key> "Retest Cypress OK"`
+8. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] All E2E tests passing
+- [ ] No new test failures
+- [ ] Test coverage maintained
+- [ ] No flaky tests introduced
+
+## Notes
+
+Automated tests are the safety net for refactoring. All tests must pass before proceeding. Any new failure indicates a regression that must be fixed.

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

@@ -0,0 +1,29 @@
+# Retest Cypress
+
+## Role
+
+Re-executer tous les tests E2E automatises pour s'assurer que le refactoring n'a pas introduit de regressions.
+
+## Actions
+
+1. Executer la suite complete de tests Cypress : npx cypress run
+2. Comparer les resultats avec l'execution pre-refactoring
+3. Si nouveaux echecs : identifier la cause (probleme de test ou de code)
+4. Corriger toute regression avant de continuer
+5. Commiter les corrections de tests si necessaire
+6. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+7. Documenter : `autocode comment <key> "Retest Cypress OK"`
+8. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Tous les tests E2E passants
+- [ ] Pas de nouveaux echecs de tests
+- [ ] Couverture de tests maintenue
+- [ ] Pas de tests flaky introduits
+
+## Notes
+
+Les tests automatises sont le filet de securite du refactoring. Tous les tests doivent passer avant de continuer. Tout nouvel echec indique une regression qui doit etre corrigee.

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

@@ -0,0 +1,30 @@
+# Retest Playwright
+
+## Role
+
+Post-refactoring validation with Playwright. Verify that refactoring did not break functionality.
+
+## Actions
+
+1. Launch application locally
+2. Re-run same scenarios as initial testing
+3. Verify nominal scenario still works
+4. Verify edge cases still work
+5. Compare behavior with pre-refactoring state
+6. If regression detected: return to review step
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+8. Document: `autocode comment <key> "Retest Playwright OK"`
+9. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] All previously passing scenarios still pass
+- [ ] No regressions introduced
+- [ ] Performance not degraded
+- [ ] No new console errors
+
+## Notes
+
+This step ensures refactoring safety. If any regression is found, the issue must return to the appropriate review step for correction.

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

@@ -0,0 +1,30 @@
+# Retest Playwright
+
+## Role
+
+Validation post-refactoring avec Playwright. Verifier que le refactoring n'a pas casse les fonctionnalites.
+
+## Actions
+
+1. Lancer l'application localement
+2. Re-executer les memes scenarios que le test initial
+3. Verifier que le scenario nominal fonctionne toujours
+4. Verifier que les cas limites fonctionnent toujours
+5. Comparer le comportement avec l'etat pre-refactoring
+6. Si regression detectee : retour a l'etape de review
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
+8. Documenter : `autocode comment <key> "Retest Playwright OK"`
+9. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Tous les scenarios passants precedemment passent toujours
+- [ ] Pas de regressions introduites
+- [ ] Performance non degradee
+- [ ] Pas de nouvelles erreurs console
+
+## Notes
+
+Cette etape assure la securite du refactoring. Si une regression est trouvee, l'issue doit retourner a l'etape de review appropriee pour correction.

package/templates/prompts/retest.en.md

@@ -0,0 +1,31 @@
+# Retest
+
+## Role
+
+Re-run all tests after bug fixes or corrections. Ensure no regressions were introduced.
+
+## Actions
+
+1. Review what was fixed/changed
+2. Run unit tests: `npm test`
+3. Run integration tests if applicable
+4. Run E2E tests if applicable
+5. Verify the original issue is fixed
+6. Check for regressions in related functionality
+7. If tests fail: return to appropriate column for fixes
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. Document: `autocode comment <key> "Retest passed: all tests green"`
+10. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] All tests pass
+- [ ] Original issue is fixed
+- [ ] No regressions detected
+- [ ] Related features still work
+
+## Notes
+
+Retest is crucial after any fix. Don't skip it even for "small" changes. Regressions are expensive.

package/templates/prompts/retest.fr.md

@@ -0,0 +1,31 @@
+# Retest
+
+## Role
+
+Re-executer tous les tests apres corrections de bugs. S'assurer qu'aucune regression n'a ete introduite.
+
+## Actions
+
+1. Revoir ce qui a ete corrige/modifie
+2. Executer les tests unitaires : `npm test`
+3. Executer les tests d'integration si applicable
+4. Executer les tests E2E si applicable
+5. Verifier que le probleme original est corrige
+6. Verifier les regressions dans les fonctionnalites liees
+7. Si les tests echouent : retourner a la colonne appropriee pour corrections
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+9. Documenter : `autocode comment <key> "Retest OK : tous les tests verts"`
+10. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Tous les tests passent
+- [ ] Le probleme original est corrige
+- [ ] Aucune regression detectee
+- [ ] Les fonctionnalites liees fonctionnent toujours
+
+## Notes
+
+Le retest est crucial apres toute correction. Ne pas le sauter meme pour des changements "mineurs". Les regressions coutent cher.

package/templates/{columns/03_review-best-practices.en.md → prompts/review-best-practices.en.md}

@@ -13,7 +13,7 @@ Code quality audit. Verify conventions and best practices are followed.
 5. Verify import organization
 6. Fix violations found
 7. Commit + push corrections
-8. If out of scope work detected: `autocode new <title> <description>`
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 9. Document: `autocode comment <key> "Review best practices OK"`
 10. Advance: `autocode next <key>`
 

package/templates/{columns/03_review-best-practices.fr.md → prompts/review-best-practices.fr.md}

@@ -13,7 +13,7 @@ Audit qualite du code. Verifier que les conventions et bonnes pratiques sont res
 5. Verifier l'organisation des imports
 6. Corriger les violations trouvees
 7. Commit + push des corrections
-8. Si travail hors scope detecte : `autocode new <title> <description>`
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 9. Documenter : `autocode comment <key> "Review best practices OK"`
 10. Avancer : `autocode next <key>`
 

package/templates/prompts/review-code.en.md

@@ -0,0 +1,31 @@
+# Review Code
+
+## Role
+
+Perform peer code review. Ensure code quality, readability, and adherence to project standards.
+
+## Actions
+
+1. Review all changed files in the ticket
+2. Check code readability and naming conventions
+3. Verify logic correctness
+4. Look for potential bugs or edge cases
+5. Check error handling
+6. Suggest improvements if needed
+7. If issues found: add comment with feedback and return to dev
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. Document: `autocode comment <key> "Code review passed: <summary>"`
+10. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Code is readable and well-organized
+- [ ] Naming is clear and consistent
+- [ ] No obvious bugs or logic errors
+- [ ] Error handling is appropriate
+
+## Notes
+
+Be constructive in feedback. Focus on significant issues, not style preferences. Approve when good enough, not perfect.

package/templates/prompts/review-code.fr.md

@@ -0,0 +1,31 @@
+# Review Code
+
+## Role
+
+Effectuer une revue de code. Assurer la qualite du code, sa lisibilite et le respect des standards du projet.
+
+## Actions
+
+1. Revoir tous les fichiers modifies dans le ticket
+2. Verifier la lisibilite du code et les conventions de nommage
+3. Verifier la justesse de la logique
+4. Rechercher les bugs potentiels ou cas limites
+5. Verifier la gestion des erreurs
+6. Suggerer des ameliorations si necessaire
+7. Si problemes trouves : ajouter un commentaire avec feedback et retourner au dev
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+9. Documenter : `autocode comment <key> "Code review OK : <resume>"`
+10. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Le code est lisible et bien organise
+- [ ] Le nommage est clair et consistant
+- [ ] Pas de bugs ou erreurs de logique evidents
+- [ ] La gestion des erreurs est appropriee
+
+## Notes
+
+Etre constructif dans les retours. Se concentrer sur les problemes significatifs, pas les preferences de style. Approuver quand c'est assez bon, pas parfait.

package/templates/{columns/05_review-consistency.en.md → prompts/review-consistency.en.md}

@@ -13,7 +13,7 @@ Verify code integrates harmoniously with existing project architecture.
 5. Verify correct Pinia store usage
 6. Fix inconsistencies
 7. Commit + push
-8. If out of scope work detected: `autocode new <title> <description>`
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 9. Document: `autocode comment <key> "Review consistency OK"`
 10. Advance: `autocode next <key>`
 

package/templates/{columns/05_review-consistency.fr.md → prompts/review-consistency.fr.md}

@@ -13,7 +13,7 @@ Verifier que le code s'integre harmonieusement avec l'architecture existante du
 5. Verifier l'usage correct des stores Pinia
 6. Corriger les incoherences
 7. Commit + push
-8. Si travail hors scope detecte : `autocode new <title> <description>`
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 9. Documenter : `autocode comment <key> "Review consistency OK"`
 10. Avancer : `autocode next <key>`
 

package/templates/{columns/04_review-no-duplication.en.md → prompts/review-no-duplication.en.md}

@@ -13,7 +13,7 @@ Identify and eliminate code duplication. Factor into reusable functions/composab
 5. Extract to composable/service/shared function if >2 usages
 6. Update all existing calls
 7. Commit + push
-8. If out of scope work detected: `autocode new <title> <description>`
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 9. Document: `autocode comment <key> "Review no duplication OK"`
 10. Advance: `autocode next <key>`
 

package/templates/{columns/04_review-no-duplication.fr.md → prompts/review-no-duplication.fr.md}

@@ -13,7 +13,7 @@ Identifier et eliminer la duplication de code. Factoriser en fonctions/composabl
 5. Extraire en composable/service/fonction partagee si >2 usages
 6. Mettre a jour tous les appels existants
 7. Commit + push
-8. Si travail hors scope detecte : `autocode new <title> <description>`
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 9. Documenter : `autocode comment <key> "Review no duplication OK"`
 10. Avancer : `autocode next <key>`
 

package/templates/{columns/06_review-security.en.md → prompts/review-security.en.md}

@@ -14,7 +14,7 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
 6. Audit API calls (injection, XSS)
 7. Fix vulnerabilities
 8. Commit + push
-9. If out of scope work detected: `autocode new <title> <description>`
+9. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 10. Document: `autocode comment <key> "Review security OK"`
 11. Advance: `autocode next <key>`
 

package/templates/{columns/06_review-security.fr.md → prompts/review-security.fr.md}

@@ -14,7 +14,7 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
 6. Auditer les appels API (injection, XSS)
 7. Corriger les vulnerabilites
 8. Commit + push
-9. Si travail hors scope detecte : `autocode new <title> <description>`
+9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 10. Documenter : `autocode comment <key> "Review security OK"`
 11. Avancer : `autocode next <key>`
 

package/templates/prompts/specification.en.md

@@ -0,0 +1,30 @@
+# Specification
+
+## Role
+
+Write detailed technical specifications for the ticket. Define the implementation approach clearly.
+
+## Actions
+
+1. Analyze the qualified requirement
+2. Define the technical architecture/approach
+3. List files to create or modify
+4. Define data structures if applicable
+5. Specify API contracts if applicable
+6. Document edge cases and error handling
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+8. Document: `autocode comment <key> "Specification complete: <technical approach>"`
+9. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Technical approach is documented
+- [ ] Files to modify are identified
+- [ ] Edge cases are considered
+- [ ] Implementation is feasible within scope
+
+## Notes
+
+Good specifications reduce back-and-forth during development. Be specific but not over-detailed.

package/templates/prompts/specification.fr.md

@@ -0,0 +1,30 @@
+# Specification
+
+## Role
+
+Rediger les specifications techniques detaillees pour le ticket. Definir clairement l'approche d'implementation.
+
+## Actions
+
+1. Analyser le besoin qualifie
+2. Definir l'architecture/approche technique
+3. Lister les fichiers a creer ou modifier
+4. Definir les structures de donnees si applicable
+5. Specifier les contrats API si applicable
+6. Documenter les cas limites et la gestion d'erreurs
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+8. Documenter : `autocode comment <key> "Specification terminee : <approche technique>"`
+9. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] L'approche technique est documentee
+- [ ] Les fichiers a modifier sont identifies
+- [ ] Les cas limites sont consideres
+- [ ] L'implementation est faisable dans le scope
+
+## Notes
+
+De bonnes specifications reduisent les allers-retours pendant le developpement. Etre specifique mais pas sur-detaille.

package/templates/{columns/08_testing-cypress.en.md → prompts/testing-cypress.en.md}

@@ -13,7 +13,7 @@ Write AND execute E2E automated tests to prevent regressions.
 5. Execute tests: npx cypress run
 6. If failures: fix tests or code
 7. Commit + push tests
-8. If out of scope work detected: `autocode new <title> <description>`
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 9. Document: `autocode comment <key> "Cypress tests OK"`
 10. Advance: `autocode next <key>`
 

package/templates/{columns/08_testing-cypress.fr.md → prompts/testing-cypress.fr.md}

@@ -13,7 +13,7 @@ Rediger ET executer des tests E2E automatises pour prevenir les regressions.
 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 : `autocode new <title> <description>`
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 9. Documenter : `autocode comment <key> "Tests Cypress OK"`
 10. Avancer : `autocode next <key>`
 

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

@@ -0,0 +1,32 @@
+# Testing Integration
+
+## Role
+
+Run integration tests to verify components work correctly together. Ensure system-level functionality.
+
+## Actions
+
+1. Identify integration points to test
+2. Run existing integration test suite
+3. Add new integration tests if needed
+4. Test API integrations
+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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+10. Document: `autocode comment <key> "Integration tests passed"`
+11. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] All integration tests pass
+- [ ] API contracts verified
+- [ ] Database operations work correctly
+- [ ] External services respond as expected
+
+## Notes
+
+Integration tests are slower but catch issues unit tests miss. Focus on critical paths and data flows.

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

@@ -0,0 +1,32 @@
+# Testing Integration
+
+## Role
+
+Executer les tests d'integration pour verifier que les composants fonctionnent correctement ensemble. Assurer la fonctionnalite au niveau systeme.
+
+## Actions
+
+1. Identifier les points d'integration a tester
+2. Executer la suite de tests d'integration existante
+3. Ajouter de nouveaux tests d'integration si necessaire
+4. Tester les integrations API
+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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+10. Documenter : `autocode comment <key> "Tests d'integration OK"`
+11. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Tous les tests d'integration passent
+- [ ] Les contrats API sont verifies
+- [ ] Les operations base de donnees fonctionnent
+- [ ] Les services externes repondent comme attendu
+
+## Notes
+
+Les tests d'integration sont plus lents mais detectent des problemes que les tests unitaires ratent. Se concentrer sur les chemins critiques et flux de donnees.

package/templates/{columns/07_testing-playwright.en.md → prompts/testing-playwright.en.md}

@@ -12,7 +12,7 @@ Live functional testing with Playwright. Manually verify feature works by naviga
 4. Test edge cases
 5. Verify error handling
 6. Capture screenshots if needed
-7. If out of scope work detected: `autocode new <title> <description>`
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 8. Document: `autocode comment <key> "Playwright tests OK"`
 9. Advance: `autocode next <key>`
 

package/templates/{columns/07_testing-playwright.fr.md → prompts/testing-playwright.fr.md}

@@ -12,7 +12,7 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
 4. Tester les cas limites
 5. Verifier la gestion d'erreurs
 6. Capturer des screenshots si necessaire
-7. Si travail hors scope detecte : `autocode new <title> <description>`
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 8. Documenter : `autocode comment <key> "Tests Playwright OK"`
 9. Avancer : `autocode next <key>`
 

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

@@ -0,0 +1,32 @@
+# Testing Unit
+
+## Role
+
+Write and run unit tests for the implemented feature. Ensure code coverage and reliability.
+
+## Actions
+
+1. Identify functions/components to test
+2. Write unit tests covering happy path
+3. Write tests for edge cases
+4. Write tests for error scenarios
+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: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+10. Document: `autocode comment <key> "Unit tests passed: <coverage>%"`
+11. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] All new code has unit tests
+- [ ] Happy path is covered
+- [ ] Edge cases are tested
+- [ ] All tests pass
+
+## Notes
+
+Good unit tests are fast, isolated, and deterministic. Test behavior, not implementation details.

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

@@ -0,0 +1,32 @@
+# Testing Unit
+
+## Role
+
+Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assurer la couverture de code et la fiabilite.
+
+## Actions
+
+1. Identifier les fonctions/composants a tester
+2. Ecrire les tests unitaires couvrant le cas nominal
+3. Ecrire les tests pour les cas limites
+4. Ecrire les tests pour les scenarios d'erreur
+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 : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+10. Documenter : `autocode comment <key> "Tests unitaires OK : <couverture>%"`
+11. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Tout le nouveau code a des tests unitaires
+- [ ] Le cas nominal est couvert
+- [ ] Les cas limites sont testes
+- [ ] Tous les tests passent
+
+## Notes
+
+De bons tests unitaires sont rapides, isoles et deterministes. Tester le comportement, pas les details d'implementation.