@autocode-cli/autocode 0.1.15 → 0.1.17

package/templates/prompts/design.en.md

@@ -15,11 +15,11 @@ Create technical and/or UX design for the feature. Prepare mockups, diagrams, or
 7. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-8. Document: `autocode comment <ticket-key> "Design complete: <summary>"`
-9. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+8. Document: `autocode comment <issue-key> "Design complete: <summary>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 
@@ -30,4 +30,4 @@ Create technical and/or UX design for the feature. Prepare mockups, diagrams, or
 
 ## Notes
 
-Good design prevents costly refactoring later. Balance thoroughness with pragmatism based on ticket complexity.
+Good design prevents costly refactoring later. Balance thoroughness with pragmatism based on issue complexity.

package/templates/prompts/design.fr.md

@@ -16,10 +16,10 @@ Creer le design technique et/ou UX pour la fonctionnalite. Preparer les maquette
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <ticket-key> "Design termine : <resume>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Design termine : <resume>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/dev.en.md

@@ -15,11 +15,11 @@ Implement the feature or fix according to specifications. Write clean, maintaina
 7. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-8. Document: `autocode comment <ticket-key> "Development complete: <files modified>"`
-9. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+8. Document: `autocode comment <issue-key> "Development complete: <files modified>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/dev.fr.md

@@ -16,10 +16,10 @@ Implementer la fonctionnalite ou le correctif selon les specifications. Ecrire d
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <ticket-key> "Developpement termine : <fichiers modifies>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Developpement termine : <fichiers modifies>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/done.en.md

@@ -2,19 +2,19 @@
 
 ## Role
 
-Archive of completed and validated tickets. End of workflow.
+Archive of completed and validated issues. End of workflow.
 
 ## Actions
 
-1. Document: `autocode comment <ticket-key> "Ticket completed"`
+1. Document: `autocode comment <issue-key> "Issue completed"`
 
-> If problem discovered: `autocode move <ticket-key> <target-column-slug>` or create a new ticket:
+> If problem discovered: `autocode move <issue-key> <target-column-slug>` or create a new issue:
 >   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
 >   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
 
 ## Validation Criteria
 
-Ticket should only arrive here if:
+Issue should only arrive here if:
 - [x] All previous steps validated
 - [x] Feature is deployed and tested
 - [x] Documentation is up to date
@@ -22,4 +22,4 @@ Ticket should only arrive here if:
 
 ## Notes
 
-Never take a ticket from this column. If a problem is discovered on a "Done" ticket, create a new ticket to handle it.
+Never take an issue from this column. If a problem is discovered on a "Done" issue, create a new issue to handle it.

package/templates/prompts/done.fr.md

@@ -6,9 +6,9 @@ Archive des tickets termines et valides. Fin du workflow.
 
 ## Actions
 
-1. Documenter : `autocode comment <ticket-key> "Ticket termine"`
+1. Documenter : `autocode comment <issue-key> "Ticket termine"`
 
-> Si probleme decouvert : `autocode move <ticket-key> <target-column-slug>` ou creer un nouveau ticket :
+> Si probleme decouvert : `autocode move <issue-key> <target-column-slug>` ou creer un nouveau ticket :
 >   - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
 >   - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
 

package/templates/prompts/error-handling-review.en.md

@@ -6,7 +6,7 @@ Verify errors are correctly handled throughout the code.
 ## Actions
 1. Analyze critical files:
    - src/server/api.ts (REST endpoints)
-   - src/core/ticket.ts (file operations)
+   - src/core/issue.ts (file operations)
    - src/services/claude.ts (external calls)
 2. Check patterns:
    - try/catch around I/O

package/templates/prompts/error-handling-review.fr.md

@@ -6,7 +6,7 @@ Vérifier que les erreurs sont correctement gérées dans tout le code.
 ## Actions
 1. Analyser les fichiers critiques:
    - src/server/api.ts (endpoints REST)
-   - src/core/ticket.ts (opérations fichiers)
+   - src/core/issue.ts (opérations fichiers)
    - src/services/claude.ts (appels externes)
 2. Vérifier les patterns:
    - try/catch autour des I/O

package/templates/prompts/file-watcher-test.en.md

@@ -5,11 +5,11 @@ Verify file monitoring system works correctly.
 
 ## Actions
 1. Start server with watcher: `node dist/index.js serve`
-2. Create a new ticket file in .autocode/tickets/
+2. Create a new issue file in .autocode/issues/
 3. Verify dashboard detects the change
-4. Modify an existing ticket
+4. Modify an existing issue
 5. Verify real-time update via WebSocket
-6. Delete a ticket
+6. Delete an issue
 7. Test with many files (performance)
 
 ## Validation Criteria
@@ -17,4 +17,4 @@ Verify file monitoring system works correctly.
 - [ ] Modification detected and propagated
 - [ ] Deletion detected
 - [ ] No memory leak on prolonged watch
-- [ ] Acceptable performance with 100+ tickets
+- [ ] Acceptable performance with 100+ issues

package/templates/prompts/file-watcher-test.fr.md

@@ -5,7 +5,7 @@ Vérifier que le système de surveillance des fichiers fonctionne correctement.
 
 ## Actions
 1. Démarrer le serveur avec watcher: `node dist/index.js serve`
-2. Créer un nouveau fichier ticket dans .autocode/tickets/
+2. Créer un nouveau fichier ticket dans .autocode/issues/
 3. Vérifier que le dashboard détecte le changement
 4. Modifier un ticket existant
 5. Vérifier la mise à jour en temps réel via WebSocket

package/templates/prompts/git-commit.en.md

@@ -14,20 +14,20 @@ Create a clean, atomic git commit for the changes. Follow conventional commit fo
    - `docs:` for documentation
    - `refactor:` for refactoring
    - `test:` for tests
-4. Include ticket key in commit body
+4. Include issue key in commit body
 5. Create commit: `git commit -m "<type>: <description>"`
 6. Verify commit: `git log -1`
-7. Document: `autocode comment <ticket-key> "Committed: <commit hash>"`
-8. Advance: `autocode next <ticket-key>`
+7. Document: `autocode comment <issue-key> "Committed: <commit hash>"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 
 - [ ] Commit message follows convention
 - [ ] Only relevant files included
 - [ ] Commit is atomic (single purpose)
-- [ ] Ticket key referenced
+- [ ] Issue key referenced
 
 ## Notes
 

package/templates/prompts/git-commit.fr.md

@@ -17,10 +17,10 @@ Creer un commit git propre et atomique pour les changements. Suivre le format co
 4. Inclure la cle du ticket dans le corps du commit
 5. Creer le commit : `git commit -m "<type>: <description>"`
 6. Verifier le commit : `git log -1`
-7. Documenter : `autocode comment <ticket-key> "Commite : <hash du commit>"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Commite : <hash du commit>"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/git-push.en.md

@@ -13,10 +13,10 @@ Push committed changes to the remote repository. Ensure CI/CD pipelines pass.
 5. Verify push succeeded
 6. Check CI/CD pipeline status
 7. If pipeline fails: fix issues and re-push
-8. Document: `autocode comment <ticket-key> "Pushed to <branch>"`
-9. Advance: `autocode next <ticket-key>`
+8. Document: `autocode comment <issue-key> "Pushed to <branch>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/git-push.fr.md

@@ -13,10 +13,10 @@ Pousser les changements commites vers le depot distant. S'assurer que les pipeli
 5. Verifier que le push a reussi
 6. Verifier le statut du pipeline CI/CD
 7. Si le pipeline echoue : corriger les problemes et re-pousser
-8. Documenter : `autocode comment <ticket-key> "Pousse vers <branche>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Pousse vers <branche>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/git-tag.en.md

@@ -14,10 +14,10 @@ Create a version tag for the release. Follow semantic versioning.
 3. Create annotated tag: `git tag -a v<version> -m "<release notes>"`
 4. Push tag: `git push origin v<version>`
 5. Verify tag on remote
-6. Document: `autocode comment <ticket-key> "Tagged: v<version>"`
-7. Advance: `autocode next <ticket-key>`
+6. Document: `autocode comment <issue-key> "Tagged: v<version>"`
+7. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/git-tag.fr.md

@@ -14,10 +14,10 @@ Creer un tag de version pour la release. Suivre le versionnement semantique.
 3. Creer un tag annote : `git tag -a v<version> -m "<notes de release>"`
 4. Pousser le tag : `git push origin v<version>`
 5. Verifier le tag sur le distant
-6. Documenter : `autocode comment <ticket-key> "Tag cree : v<version>"`
-7. Avancer : `autocode next <ticket-key>`
+6. Documenter : `autocode comment <issue-key> "Tag cree : v<version>"`
+7. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/in-progress.en.md

@@ -2,11 +2,11 @@
 
 ## Role
 
-Active development. Ticket is being worked on, code is being written.
+Active development. Issue is being worked on, code is being written.
 
 ## Actions
 
-1. Analyze ticket and acceptance criteria
+1. Analyze issue and acceptance criteria
 2. Explore codebase to understand existing context
 3. Plan modifications (files to create/modify)
 4. Implement the solution
@@ -14,11 +14,11 @@ Active development. Ticket is being worked on, code is being written.
 6. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-7. Document: `autocode comment <ticket-key> "Work completed"`
-8. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+7. Document: `autocode comment <issue-key> "Work completed"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/in-progress.fr.md

@@ -15,10 +15,10 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-7. Documenter : `autocode comment <ticket-key> "Travail effectue"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Travail effectue"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/qualification.en.md

@@ -2,24 +2,24 @@
 
 ## Role
 
-Analyze and qualify the ticket requirement. Ensure the request is clear, feasible, and properly scoped.
+Analyze and qualify the issue requirement. Ensure the request is clear, feasible, and properly scoped.
 
 ## Actions
 
-1. Read the ticket description and acceptance criteria
+1. Read the issue 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
+5. Identify dependencies with other issues or systems
 6. If clarification needed: add comment with questions
 7. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-8. Document: `autocode comment <ticket-key> "Qualification complete: <summary>"`
-9. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+8. Document: `autocode comment <issue-key> "Qualification complete: <summary>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 
@@ -30,4 +30,4 @@ Analyze and qualify the ticket requirement. Ensure the request is clear, feasibl
 
 ## Notes
 
-A well-qualified ticket saves development time. When in doubt, ask for clarification rather than assuming.
+A well-qualified issue saves development time. When in doubt, ask for clarification rather than assuming.

package/templates/prompts/qualification.fr.md

@@ -16,10 +16,10 @@ Analyser et qualifier le besoin du ticket. S'assurer que la demande est claire,
    - Legerement hors scope (amelioration mineure, cas limite) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column ready`
    - Tres hors scope (nouvelle feature, changement majeur) : `autocode new "<titre>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteres>" --semver patch --column backlog`
    - Dans le scope : traiter directement dans le ticket actuel
-8. Documenter : `autocode comment <ticket-key> "Qualification terminee : <resume>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Qualification terminee : <resume>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -10,10 +10,10 @@ Re-run all automated E2E tests to ensure refactoring did not introduce regressio
 2. Compare results with pre-refactoring run
 3. If new failures: identify cause (test or code issue)
 4. Fix any regressions before proceeding
-5. Document: `autocode comment <ticket-key> "Retest Cypress OK"`
-6. Advance: `autocode next <ticket-key>`
+5. Document: `autocode comment <issue-key> "Retest Cypress OK"`
+6. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

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

@@ -10,10 +10,10 @@ Re-executer tous les tests E2E automatises pour s'assurer que le refactoring n'a
 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. Documenter : `autocode comment <ticket-key> "Retest Cypress OK"`
-6. Avancer : `autocode next <ticket-key>`
+5. Documenter : `autocode comment <issue-key> "Retest Cypress OK"`
+6. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -12,11 +12,11 @@ Post-refactoring validation with Playwright. Verify that refactoring did not bre
 4. Verify edge cases still work
 5. Compare behavior with pre-refactoring state
 6. If regression detected: return to review step
-7. Do not test functionality outside the ticket scope
-8. Document: `autocode comment <ticket-key> "Retest Playwright OK"`
-9. Advance: `autocode next <ticket-key>`
+7. Do not test functionality outside the issue scope
+8. Document: `autocode comment <issue-key> "Retest Playwright OK"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,10 @@ Validation post-refactoring avec Playwright. Verifier que le refactoring n'a pas
 5. Comparer le comportement avec l'etat pre-refactoring
 6. Si regression detectee : retour a l'etape de review
 7. Ne pas tester de fonctionnalites hors scope du ticket
-8. Documenter : `autocode comment <ticket-key> "Retest Playwright OK"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Retest Playwright OK"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/retest.en.md

@@ -13,11 +13,11 @@ Re-run all tests after bug fixes or corrections. Ensure no regressions were intr
 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. Do not write tests for code outside the ticket scope
-9. Document: `autocode comment <ticket-key> "Retest passed: all tests green"`
-10. Advance: `autocode next <ticket-key>`
+8. Do not write tests for code outside the issue scope
+9. Document: `autocode comment <issue-key> "Retest passed: all tests green"`
+10. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/retest.fr.md

@@ -14,10 +14,10 @@ Re-executer tous les tests apres corrections de bugs. S'assurer qu'aucune regres
 6. Verifier les regressions dans les fonctionnalites liees
 7. Si les tests echouent : retourner a la colonne appropriee pour corrections
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <ticket-key> "Retest OK : tous les tests verts"`
-10. Avancer : `autocode next <ticket-key>`
+9. Documenter : `autocode comment <issue-key> "Retest OK : tous les tests verts"`
+10. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-best-practices.en.md

@@ -12,10 +12,10 @@ Code quality audit. Verify conventions and best practices are followed.
 4. Verify file size (components < 300 lines)
 5. Verify import organization
 6. Fix violations found
-7. Document: `autocode comment <ticket-key> "Review best practices OK"`
-8. Advance: `autocode next <ticket-key>`
+7. Document: `autocode comment <issue-key> "Review best practices OK"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-best-practices.fr.md

@@ -12,10 +12,10 @@ Audit qualite du code. Verifier que les conventions et bonnes pratiques sont res
 4. Verifier la taille des fichiers (composants < 300 lignes)
 5. Verifier l'organisation des imports
 6. Corriger les violations trouvees
-7. Documenter : `autocode comment <ticket-key> "Review best practices OK"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Review best practices OK"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -6,17 +6,17 @@ Perform peer code review. Ensure code quality, readability, and adherence to pro
 
 ## Actions
 
-1. Review all changed files in the ticket
+1. Review all changed files in the issue
 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. Document: `autocode comment <ticket-key> "Code review passed: <summary>"`
-9. Advance: `autocode next <ticket-key>`
+8. Document: `autocode comment <issue-key> "Code review passed: <summary>"`
+9. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,10 @@ Effectuer une revue de code. Assurer la qualite du code, sa lisibilite et le res
 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. Documenter : `autocode comment <ticket-key> "Code review OK : <resume>"`
-9. Avancer : `autocode next <ticket-key>`
+8. Documenter : `autocode comment <issue-key> "Code review OK : <resume>"`
+9. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -12,10 +12,10 @@ Verify code integrates harmoniously with existing project architecture.
 4. Check error handling (uniform try/catch)
 5. Verify correct Pinia store usage
 6. Fix inconsistencies
-7. Document: `autocode comment <ticket-key> "Review consistency OK"`
-8. Advance: `autocode next <ticket-key>`
+7. Document: `autocode comment <issue-key> "Review consistency OK"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

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

@@ -12,10 +12,10 @@ Verifier que le code s'integre harmonieusement avec l'architecture existante du
 4. Controler la gestion d'erreurs (try/catch uniforme)
 5. Verifier l'usage correct des stores Pinia
 6. Corriger les incoherences
-7. Documenter : `autocode comment <ticket-key> "Review consistency OK"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Review consistency OK"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

package/templates/prompts/review-no-duplication.en.md

@@ -12,10 +12,10 @@ Identify and eliminate code duplication. Factor into reusable functions/composab
 4. Detect copy-pasted business logic
 5. Extract to composable/service/shared function if >2 usages
 6. Update all existing calls
-7. Document: `autocode comment <ticket-key> "Review no duplication OK"`
-8. Advance: `autocode next <ticket-key>`
+7. Document: `autocode comment <issue-key> "Review no duplication OK"`
+8. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria
 

package/templates/prompts/review-no-duplication.fr.md

@@ -12,10 +12,10 @@ Identifier et eliminer la duplication de code. Factoriser en fonctions/composabl
 4. Detecter la logique metier copiee-collee
 5. Extraire en composable/service/fonction partagee si >2 usages
 6. Mettre a jour tous les appels existants
-7. Documenter : `autocode comment <ticket-key> "Review no duplication OK"`
-8. Avancer : `autocode next <ticket-key>`
+7. Documenter : `autocode comment <issue-key> "Review no duplication OK"`
+8. Avancer : `autocode next <issue-key>`
 
-> Ou retour : `autocode move <ticket-key> <target-column-slug>`
+> Ou retour : `autocode move <issue-key> <target-column-slug>`
 
 ## Criteres de Validation
 

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

@@ -16,11 +16,11 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
 8. If out of scope work detected:
    - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
    - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
-   - In scope: handle directly in current ticket
-9. Document: `autocode comment <ticket-key> "Review security OK"`
-10. Advance: `autocode next <ticket-key>`
+   - In scope: handle directly in current issue
+9. Document: `autocode comment <issue-key> "Review security OK"`
+10. Advance: `autocode next <issue-key>`
 
-> Or return: `autocode move <ticket-key> <target-column-slug>`
+> Or return: `autocode move <issue-key> <target-column-slug>`
 
 ## Validation Criteria