@autocode-cli/autocode 0.22.0 → 0.23.0

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

@@ -13,10 +13,7 @@ Perform peer code review. Ensure code quality, readability, and adherence to pro
 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 <issue-key> "Code review passed: <summary>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Code review: [passed/issues found] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,7 @@ 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 <issue-key> "Code review OK : <resume>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Code review : [OK/Problemes trouves] - <resume>"`
 
 ## Criteres de Validation
 

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

@@ -12,10 +12,7 @@ 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 <issue-key> "Review consistency OK"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Consistency review: [passed/issues found] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -12,10 +12,7 @@ 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 <issue-key> "Review consistency OK"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Review consistency : [OK/problemes] - <resume>"`
 
 ## Criteres de Validation
 

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

@@ -12,10 +12,7 @@ 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 <issue-key> "Review no duplication OK"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Duplication review: [passed/issues found] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -12,10 +12,7 @@ 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 <issue-key> "Review no duplication OK"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Review duplication : [OK/problemes] - <resume>"`
 
 ## Criteres de Validation
 

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

@@ -17,10 +17,7 @@ Security audit. Identify and fix potential vulnerabilities (OWASP Top 10).
    - 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 issue
-9. Document: `autocode comment <issue-key> "Review security OK"`
-10. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+9. Document: `autocode comment <issue-key> "Security review: [passed/issues found] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -17,10 +17,7 @@ Audit securite. Identifier et corriger les vulnerabilites potentielles (OWASP To
    - 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
-9. Documenter : `autocode comment <issue-key> "Review security OK"`
-10. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+9. Documenter : `autocode comment <issue-key> "Review security : [OK/Problemes] - <resume>"`
 
 ## Criteres de Validation
 

package/templates/prompts/specification.en.md

@@ -16,10 +16,7 @@ Write detailed technical specifications for the issue. Define the implementation
    - 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 issue
-8. Document: `autocode comment <issue-key> "Specification complete: <technical approach>"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Specification: [complete/in progress] - <technical approach>"`
 
 ## Validation Criteria
 

package/templates/prompts/specification.fr.md

@@ -16,10 +16,7 @@ Rediger les specifications techniques detaillees pour le ticket. Definir clairem
    - 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 <issue-key> "Specification terminee : <approche technique>"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Specification : [terminee/en cours] - <approche technique>"`
 
 ## Criteres de Validation
 

package/templates/prompts/splitter.en.md

@@ -21,10 +21,7 @@ If the task is small enough to be completed in one go, proceed directly without
 5. Create sub-issues: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog --parent <issue-key>`
 6. Verify no functionality has been forgotten or duplicated across issues
 7. Create an integration issue that references all sub-issues to validate cohesion
-8. Document: `autocode comment <issue-key> "[summary]"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Splitter: [summary]"`
 
 ## Validation Criteria
 

package/templates/prompts/splitter.fr.md

@@ -22,9 +22,6 @@ Si la tâche est suffisamment petite pour être complétée en une fois, procéd
 6. Vérifier qu'aucune fonctionnalité n'a été oubliée ou dupliquée entre les tickets
 7. Créer un ticket d'intégration qui référence tous les sous-tickets pour valider la cohésion
 8. Documenter : `autocode comment <issue-key> "[résumé]"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retourner : `autocode move <issue-key> <target-column-slug>`
 
 ## Critères de Validation
 

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

@@ -13,10 +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. Do not write tests for code outside the issue scope
-8. Document: `autocode comment <issue-key> "Cypress tests OK"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Cypress tests: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

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

@@ -13,10 +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. Ne pas ecrire de tests pour du code hors scope du ticket
-8. Documenter : `autocode comment <issue-key> "Tests Cypress OK"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Tests Cypress : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -14,10 +14,7 @@ Run integration tests to verify components work correctly together. Ensure syste
 6. Test external service connections
 7. Fix any failing tests
 8. Do not write tests for code outside the issue scope
-9. Document: `autocode comment <issue-key> "Integration tests passed"`
-10. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+9. Document: `autocode comment <issue-key> "Integration tests: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

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

@@ -14,10 +14,7 @@ Executer les tests d'integration pour verifier que les composants fonctionnent c
 6. Tester les connexions aux services externes
 7. Corriger les tests en echec
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <issue-key> "Tests d'integration OK"`
-10. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+9. Documenter : `autocode comment <issue-key> "Tests integration : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -13,10 +13,7 @@ Live functional testing with Playwright. Manually verify feature works by naviga
 5. Verify error handling
 6. Capture screenshots if needed
 7. Do not test functionality outside the issue scope
-8. Document: `autocode comment <issue-key> "Playwright tests OK"`
-9. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+8. Document: `autocode comment <issue-key> "Playwright tests: [passed/failed] - <details>"`
 
 ## Validation Criteria
 

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

@@ -13,10 +13,7 @@ Test fonctionnel live avec Playwright. Verifier manuellement que la feature fonc
 5. Verifier la gestion d'erreurs
 6. Capturer des screenshots si necessaire
 7. Ne pas tester de fonctionnalites hors scope du ticket
-8. Documenter : `autocode comment <issue-key> "Tests Playwright OK"`
-9. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+8. Documenter : `autocode comment <issue-key> "Tests Playwright : [OK/echecs] - <details>"`
 
 ## Criteres de Validation
 

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

@@ -14,10 +14,7 @@ Write and run unit tests for the implemented feature. Ensure code coverage and r
 6. Fix any failing tests
 7. Verify coverage meets project standards
 8. Do not write tests for code outside the issue scope
-9. Document: `autocode comment <issue-key> "Unit tests passed: <coverage>%"`
-10. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+9. Document: `autocode comment <issue-key> "Unit tests: [passed/failed] - <coverage>%"`
 
 ## Validation Criteria
 

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

@@ -14,10 +14,7 @@ Ecrire et executer les tests unitaires pour la fonctionnalite implementee. Assur
 6. Corriger les tests en echec
 7. Verifier que la couverture respecte les standards du projet
 8. Ne pas ecrire de tests pour du code hors scope du ticket
-9. Documenter : `autocode comment <issue-key> "Tests unitaires OK : <couverture>%"`
-10. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+9. Documenter : `autocode comment <issue-key> "Tests unitaires : [OK/Echecs] - <couverture>%"`
 
 ## Criteres de Validation
 

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

@@ -11,10 +11,7 @@ Document changes for future developers and users.
 3. Document new features
 4. Update existing guides if impacted
 5. Verify doc consistency
-6. Document: `autocode comment <issue-key> "Documentation updated"`
-7. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+6. Document: `autocode comment <issue-key> "Documentation: [updated/not applicable]"`
 
 ## Validation Criteria
 

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

@@ -11,10 +11,7 @@ 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. Documenter : `autocode comment <issue-key> "Documentation mise a jour"`
-7. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+6. Documenter : `autocode comment <issue-key> "Documentation : [mise a jour/non applicable]"`
 
 ## Criteres de Validation
 

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

@@ -12,10 +12,7 @@ Final validation: verify everything works in staging AND git repo is clean.
 4. Verify visually everything is OK
 5. Capture proof (screenshot)
 6. Confirm feature works
-7. Document: `autocode comment <issue-key> "Staging validation OK"`
-8. Advance: `autocode next <issue-key>`
-
-> Or return: `autocode move <issue-key> <target-column-slug>`
+7. Document: `autocode comment <issue-key> "Staging validation: [OK/failed] - <summary>"`
 
 ## Validation Criteria
 

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

@@ -12,10 +12,7 @@ Validation finale : verifier que tout fonctionne en staging ET que le repo git e
 4. Verifier visuellement que tout est OK
 5. Capturer une preuve (screenshot)
 6. Confirmer que la feature fonctionne
-7. Documenter : `autocode comment <issue-key> "Validation staging OK"`
-8. Avancer : `autocode next <issue-key>`
-
-> Ou retour : `autocode move <issue-key> <target-column-slug>`
+7. Documenter : `autocode comment <issue-key> "Validation staging : [OK/echec] - <resume>"`
 
 ## Criteres de Validation
 

package/.output/public/_nuxt/builds/meta/83d9a3fc-c99e-4e26-adef-e7f5b329b81a.json

@@ -1 +0,0 @@
-{"id":"83d9a3fc-c99e-4e26-adef-e7f5b329b81a","timestamp":1767659950446,"matcher":{"static":{},"wildcard":{},"dynamic":{}},"prerendered":["/"]}

package/.output/server/chunks/_/comments.service.mjs

@@ -1,26 +0,0 @@
-import { i as debug, p as prisma } from '../nitro/nitro.mjs';
-
-async function findByIssue(issueKey) {
-  debug("comments", "findByIssue", { issueKey });
-  return prisma.comment.findMany({
-    where: { issueKey },
-    orderBy: { createdAt: "desc" }
-  });
-}
-async function create(issueKey, data) {
-  const id = String(Date.now());
-  debug("comments", "create", { issueKey, author: data.author, contentLength: data.content.length });
-  const comment = await prisma.comment.create({
-    data: {
-      id,
-      issueKey,
-      content: data.content,
-      author: data.author
-    }
-  });
-  debug("comments", "created", { id: comment.id, issueKey });
-  return comment;
-}
-
-export { create as c, findByIssue as f };
-//# sourceMappingURL=comments.service.mjs.map

package/.output/server/chunks/_/comments.service.mjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"comments.service.mjs","sources":["../../../../server/services/comments.service.ts"],"names":[],"mappings":";;AAYA,eAAsB,YAAY,QAAA,EAAsC;AACtE,EAAA,KAAA,CAAM,UAAA,EAAY,aAAA,EAAe,EAAE,QAAA,EAAU,CAAA;AAC7C,EAAA,OAAO,MAAA,CAAO,QAAQ,QAAA,CAAS;AAAA,IAC7B,KAAA,EAAO,EAAE,QAAA,EAAS;AAAA,IAClB,OAAA,EAAS,EAAE,SAAA,EAAW,MAAA;AAAO,GAC9B,CAAA;AACH;AAcA,eAAsB,MAAA,CAAO,UAAkB,IAAA,EAA4C;AACzF,EAAA,MAAM,EAAA,GAAK,MAAA,CAAO,IAAA,CAAK,GAAA,EAAK,CAAA;AAE5B,EAAA,KAAA,CAAM,UAAA,EAAY,QAAA,EAAU,EAAE,QAAA,EAAU,MAAA,EAAQ,IAAA,CAAK,MAAA,EAAQ,aAAA,EAAe,IAAA,CAAK,OAAA,CAAQ,MAAA,EAAQ,CAAA;AAEjG,EAAA,MAAM,OAAA,GAAU,MAAM,MAAA,CAAO,OAAA,CAAQ,MAAA,CAAO;AAAA,IAC1C,IAAA,EAAM;AAAA,MACJ,EAAA;AAAA,MACA,QAAA;AAAA,MACA,SAAS,IAAA,CAAK,OAAA;AAAA,MACd,QAAQ,IAAA,CAAK;AAAA;AACf,GACD,CAAA;AAED,EAAA,KAAA,CAAM,YAAY,SAAA,EAAW,EAAE,IAAI,OAAA,CAAQ,EAAA,EAAI,UAAU,CAAA;AACzD,EAAA,OAAO,OAAA;AACT;;;;"}