@autocode-cli/autocode 0.1.4 → 0.1.6

package/templates/catalog.yaml

@@ -0,0 +1,100 @@
+# AutoCode Column Catalog
+# Defines available columns for each pipeline segment
+# Columns can be selected from this catalog when configuring pipelines
+
+segments:
+  definition:
+    description: "Columns for ticket qualification and preparation"
+    columns:
+      - slug: backlog
+        name: Backlog
+        description: "Initial ticket storage before prioritization"
+      - slug: qualification
+        name: Qualification
+        description: "Analysis and qualification of the requirement"
+      - slug: specification
+        name: Specification
+        description: "Writing detailed specifications"
+      - slug: design
+        name: Design
+        description: "Technical/UX design phase"
+      - slug: ready
+        name: Ready
+        description: "Ready for development"
+
+  action:
+    description: "Columns for implementation and validation"
+    columns:
+      - slug: in-progress
+        name: In Progress
+        description: "Work currently in progress"
+      - slug: dev
+        name: Development
+        description: "Code implementation"
+      - slug: review-code
+        name: Review Code
+        description: "Peer code review"
+      - slug: review-best-practices
+        name: Review Best Practices
+        description: "Best practices verification"
+      - slug: review-no-duplication
+        name: Review No Duplication
+        description: "Check for code duplication"
+      - slug: review-consistency
+        name: Review Consistency
+        description: "Consistency verification"
+      - slug: review-security
+        name: Review Security
+        description: "Security audit"
+      - slug: testing-unit
+        name: Testing Unit
+        description: "Unit tests execution"
+      - slug: testing-playwright
+        name: Testing Playwright
+        description: "Playwright E2E tests"
+      - slug: testing-cypress
+        name: Testing Cypress
+        description: "Cypress E2E tests"
+      - slug: testing-integration
+        name: Testing Integration
+        description: "Integration tests"
+      - slug: retest-playwright
+        name: Retest Playwright
+        description: "Re-run Playwright tests after fixes"
+      - slug: retest-cypress
+        name: Retest Cypress
+        description: "Re-run Cypress tests after fixes"
+      - slug: retest
+        name: Retest
+        description: "General retest after corrections"
+
+  finish:
+    description: "Columns for finalization and deployment"
+    columns:
+      - slug: update-docs
+        name: Update Docs
+        description: "Documentation update"
+      - slug: changelog
+        name: Changelog
+        description: "Changelog update"
+      - slug: git-commit
+        name: Git Commit
+        description: "Create Git commit"
+      - slug: git-push
+        name: Git Push
+        description: "Push to remote repository"
+      - slug: git-tag
+        name: Git Tag
+        description: "Create version tag"
+      - slug: deploy-staging
+        name: Deploy Staging
+        description: "Deploy to staging environment"
+      - slug: validate-staging
+        name: Validate Staging
+        description: "Validate staging deployment"
+      - slug: deploy-prod
+        name: Deploy Production
+        description: "Deploy to production"
+      - slug: done
+        name: Done
+        description: "Completed"

package/templates/{columns/00_backlog.en.md → prompts/backlog.en.md}

@@ -12,7 +12,7 @@ Storage for new tickets. Tickets here need qualification before work can begin.
 4. Define acceptance criteria if missing
 5. Set priority (P0-P3) based on impact and urgency
 6. Identify scope and potentially affected files
-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> "Qualification done"`
 9. Advance: `autocode next <key>`
 

package/templates/{columns/00_backlog.fr.md → prompts/backlog.fr.md}

@@ -12,7 +12,7 @@ Stockage des nouveaux tickets. Les tickets ici doivent etre qualifies avant de c
 4. Definir les criteres d'acceptation si manquants
 5. Definir la priorite (P0-P3) selon l'impact et l'urgence
 6. Identifier le perimetre et les fichiers potentiellement impactes
-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> "Qualification effectuee"`
 9. Avancer : `autocode next <key>`
 

package/templates/prompts/changelog.en.md

@@ -0,0 +1,31 @@
+# Changelog
+
+## Role
+
+Update the changelog with the changes made in this ticket. Document for users and future developers.
+
+## Actions
+
+1. Review all changes made in the ticket
+2. Determine change type (Added, Changed, Fixed, Removed, Security)
+3. Open CHANGELOG.md
+4. Add entry under "Unreleased" section
+5. Use clear, user-facing language
+6. Reference ticket key if applicable
+7. Commit + push changelog update
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. Document: `autocode comment <key> "Changelog updated"`
+10. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Changelog entry added
+- [ ] Change type is correct
+- [ ] Description is clear and concise
+- [ ] Entry follows project format
+
+## Notes
+
+Write for end users, not developers. Focus on what changed from their perspective, not implementation details.

package/templates/prompts/changelog.fr.md

@@ -0,0 +1,31 @@
+# Changelog
+
+## Role
+
+Mettre a jour le changelog avec les changements effectues dans ce ticket. Documenter pour les utilisateurs et futurs developpeurs.
+
+## Actions
+
+1. Revoir tous les changements effectues dans le ticket
+2. Determiner le type de changement (Added, Changed, Fixed, Removed, Security)
+3. Ouvrir CHANGELOG.md
+4. Ajouter une entree sous la section "Unreleased"
+5. Utiliser un langage clair oriente utilisateur
+6. Referencer la cle du ticket si applicable
+7. Commit + push de la mise a jour du changelog
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+9. Documenter : `autocode comment <key> "Changelog mis a jour"`
+10. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Entree changelog ajoutee
+- [ ] Le type de changement est correct
+- [ ] La description est claire et concise
+- [ ] L'entree suit le format du projet
+
+## Notes
+
+Ecrire pour les utilisateurs finaux, pas les developpeurs. Se concentrer sur ce qui a change de leur point de vue, pas les details d'implementation.

package/templates/prompts/deploy-prod.en.md

@@ -0,0 +1,32 @@
+# Deploy Production
+
+## Role
+
+Deploy the release to production environment. Ensure zero-downtime deployment.
+
+## Actions
+
+1. Verify staging validation passed
+2. Check production environment health
+3. Create backup if applicable
+4. Deploy to production: follow project-specific process
+5. Run smoke tests on production
+6. Verify critical functionality
+7. Monitor logs for errors
+8. If issues detected: rollback immediately
+9. If out of scope work detected: `autocode new "<title>" "<description>" -p P0 -l "urgent" -a "<criteria>" -s patch`
+10. Document: `autocode comment <key> "Deployed to production: v<version>"`
+11. Advance: `autocode next <key>`
+
+> Or rollback: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Production deployment successful
+- [ ] Smoke tests pass
+- [ ] No errors in logs
+- [ ] Performance is acceptable
+
+## Notes
+
+Production deployments are critical. Have a rollback plan ready. Monitor closely for the first few minutes after deployment.

package/templates/prompts/deploy-prod.fr.md

@@ -0,0 +1,32 @@
+# Deploy Production
+
+## Role
+
+Deployer la release en environnement de production. Assurer un deploiement sans interruption.
+
+## Actions
+
+1. Verifier que la validation staging est passee
+2. Verifier la sante de l'environnement de production
+3. Creer une sauvegarde si applicable
+4. Deployer en production : suivre le processus specifique au projet
+5. Executer les smoke tests en production
+6. Verifier les fonctionnalites critiques
+7. Surveiller les logs pour les erreurs
+8. Si problemes detectes : rollback immediatement
+9. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P0 -l "urgent" -a "<criteres>" -s patch`
+10. Documenter : `autocode comment <key> "Deploye en production : v<version>"`
+11. Avancer : `autocode next <key>`
+
+> Ou rollback : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Deploiement production reussi
+- [ ] Les smoke tests passent
+- [ ] Pas d'erreurs dans les logs
+- [ ] Les performances sont acceptables
+
+## Notes
+
+Les deploiements production sont critiques. Avoir un plan de rollback pret. Surveiller attentivement les premieres minutes apres le deploiement.

package/templates/{columns/10_deploy-staging.en.md → prompts/deploy-staging.en.md}

@@ -11,7 +11,7 @@ Deploy changes to staging environment for validation.
 3. Wait for deployment to complete
 4. Verify deployment is stable
 5. Document deployed version
-6. If out of scope work detected: `autocode new <title> <description>`
+6. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 7. Document: `autocode comment <key> "Deployed to staging"`
 8. Advance: `autocode next <key>`
 

package/templates/{columns/10_deploy-staging.fr.md → prompts/deploy-staging.fr.md}

@@ -11,7 +11,7 @@ Deployer les changements sur l'environnement de staging pour validation.
 3. Attendre la fin du deploiement
 4. Verifier que le deploiement est stable
 5. Documenter la version deployee
-6. Si travail hors scope detecte : `autocode new <title> <description>`
+6. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 7. Documenter : `autocode comment <key> "Deploye en staging"`
 8. Avancer : `autocode next <key>`
 

package/templates/prompts/design.en.md

@@ -0,0 +1,30 @@
+# Design
+
+## Role
+
+Create technical and/or UX design for the feature. Prepare mockups, diagrams, or architecture documents as needed.
+
+## Actions
+
+1. Review specifications and requirements
+2. Create UI mockups/wireframes if user-facing
+3. Design component architecture if applicable
+4. Create sequence diagrams for complex flows
+5. Define state management approach if applicable
+6. Document design decisions and trade-offs
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+8. Document: `autocode comment <key> "Design complete: <summary>"`
+9. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Design addresses all requirements
+- [ ] User experience is considered
+- [ ] Technical feasibility confirmed
+- [ ] Design is documented/accessible
+
+## Notes
+
+Good design prevents costly refactoring later. Balance thoroughness with pragmatism based on ticket complexity.

package/templates/prompts/design.fr.md

@@ -0,0 +1,30 @@
+# Design
+
+## Role
+
+Creer le design technique et/ou UX pour la fonctionnalite. Preparer les maquettes, diagrammes ou documents d'architecture selon les besoins.
+
+## Actions
+
+1. Revoir les specifications et exigences
+2. Creer des maquettes UI/wireframes si interface utilisateur
+3. Designer l'architecture des composants si applicable
+4. Creer des diagrammes de sequence pour les flux complexes
+5. Definir l'approche de gestion d'etat si applicable
+6. Documenter les decisions de design et compromis
+7. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+8. Documenter : `autocode comment <key> "Design termine : <resume>"`
+9. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Le design repond a toutes les exigences
+- [ ] L'experience utilisateur est consideree
+- [ ] La faisabilite technique est confirmee
+- [ ] Le design est documente/accessible
+
+## Notes
+
+Un bon design evite des refactorisations couteuses plus tard. Equilibrer rigueur et pragmatisme selon la complexite du ticket.

package/templates/prompts/dev.en.md

@@ -0,0 +1,31 @@
+# Development
+
+## Role
+
+Implement the feature or fix according to specifications. Write clean, maintainable code.
+
+## Actions
+
+1. Review specifications and design documents
+2. Create/modify necessary files
+3. Implement the feature following coding standards
+4. Add inline comments for complex logic
+5. Handle edge cases and errors gracefully
+6. Test locally before committing
+7. Commit + push with descriptive message
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. Document: `autocode comment <key> "Development complete: <files modified>"`
+10. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Feature works as specified
+- [ ] Code follows project conventions
+- [ ] No console errors or warnings
+- [ ] Edge cases handled
+
+## Notes
+
+Write code for humans first, computers second. Keep functions small and focused. When in doubt, refactor.

package/templates/prompts/dev.fr.md

@@ -0,0 +1,31 @@
+# Developpement
+
+## Role
+
+Implementer la fonctionnalite ou le correctif selon les specifications. Ecrire du code propre et maintenable.
+
+## Actions
+
+1. Revoir les specifications et documents de design
+2. Creer/modifier les fichiers necessaires
+3. Implementer la fonctionnalite en suivant les standards de code
+4. Ajouter des commentaires pour la logique complexe
+5. Gerer les cas limites et erreurs elegamment
+6. Tester localement avant de commiter
+7. Commit + push avec message descriptif
+8. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+9. Documenter : `autocode comment <key> "Developpement termine : <fichiers modifies>"`
+10. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] La fonctionnalite fonctionne comme specifie
+- [ ] Le code suit les conventions du projet
+- [ ] Pas d'erreurs ou warnings console
+- [ ] Les cas limites sont geres
+
+## Notes
+
+Ecrire du code pour les humains d'abord, les machines ensuite. Garder les fonctions petites et focalisees. En cas de doute, refactoriser.

package/templates/{columns/12_done.en.md → prompts/done.en.md}

@@ -8,7 +8,7 @@ Archive of completed and validated tickets. End of workflow.
 
 1. Document: `autocode comment <key> "Ticket completed"`
 
-> If problem discovered: `autocode move <key> <column>` or `autocode new <title> <description>`
+> If problem discovered: `autocode move <key> <column>` or `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
 
 ## Validation Criteria
 

package/templates/{columns/12_done.fr.md → prompts/done.fr.md}

@@ -8,7 +8,7 @@ Archive des tickets termines et valides. Fin du workflow.
 
 1. Documenter : `autocode comment <key> "Ticket termine"`
 
-> Si probleme decouvert : `autocode move <key> <column>` ou `autocode new <title> <description>`
+> Si probleme decouvert : `autocode move <key> <column>` ou `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<critères>" -s patch`
 
 ## Criteres de Validation
 

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

@@ -0,0 +1,35 @@
+# Git Commit
+
+## Role
+
+Create a clean, atomic git commit for the changes. Follow conventional commit format.
+
+## Actions
+
+1. Review all staged changes: `git status`
+2. Ensure only relevant files are staged
+3. Write commit message following format:
+   - `feat:` for new features
+   - `fix:` for bug fixes
+   - `docs:` for documentation
+   - `refactor:` for refactoring
+   - `test:` for tests
+4. Include ticket key in commit body
+5. Create commit: `git commit -m "<type>: <description>"`
+6. Verify commit: `git log -1`
+7. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+8. Document: `autocode comment <key> "Committed: <commit hash>"`
+9. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Commit message follows convention
+- [ ] Only relevant files included
+- [ ] Commit is atomic (single purpose)
+- [ ] Ticket key referenced
+
+## Notes
+
+Good commits tell a story. Each commit should be a logical unit of change that could be reverted independently.

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

@@ -0,0 +1,35 @@
+# Git Commit
+
+## Role
+
+Creer un commit git propre et atomique pour les changements. Suivre le format conventional commit.
+
+## Actions
+
+1. Revoir tous les changements stages : `git status`
+2. S'assurer que seuls les fichiers pertinents sont stages
+3. Ecrire le message de commit suivant le format :
+   - `feat:` pour les nouvelles fonctionnalites
+   - `fix:` pour les corrections de bugs
+   - `docs:` pour la documentation
+   - `refactor:` pour le refactoring
+   - `test:` pour les tests
+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. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+8. Documenter : `autocode comment <key> "Commite : <hash du commit>"`
+9. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Le message de commit suit la convention
+- [ ] Seuls les fichiers pertinents sont inclus
+- [ ] Le commit est atomique (but unique)
+- [ ] La cle du ticket est referencee
+
+## Notes
+
+De bons commits racontent une histoire. Chaque commit doit etre une unite logique de changement qui pourrait etre revertee independamment.

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

@@ -0,0 +1,31 @@
+# Git Push
+
+## Role
+
+Push committed changes to the remote repository. Ensure CI/CD pipelines pass.
+
+## Actions
+
+1. Verify all commits are ready: `git log origin/main..HEAD`
+2. Pull latest changes: `git pull --rebase origin main`
+3. Resolve any conflicts if needed
+4. Push to remote: `git push origin <branch>`
+5. Verify push succeeded
+6. Check CI/CD pipeline status
+7. If pipeline fails: fix issues and re-push
+8. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+9. Document: `autocode comment <key> "Pushed to <branch>"`
+10. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Changes pushed successfully
+- [ ] No merge conflicts
+- [ ] CI/CD pipeline passes
+- [ ] Branch is up to date
+
+## Notes
+
+Always pull before push to avoid conflicts. If CI fails, fix it immediately - don't leave the build broken.

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

@@ -0,0 +1,31 @@
+# Git Push
+
+## Role
+
+Pousser les changements commites vers le depot distant. S'assurer que les pipelines CI/CD passent.
+
+## Actions
+
+1. Verifier que tous les commits sont prets : `git log origin/main..HEAD`
+2. Recuperer les derniers changements : `git pull --rebase origin main`
+3. Resoudre les conflits si necessaire
+4. Pousser vers le distant : `git push origin <branche>`
+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. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+9. Documenter : `autocode comment <key> "Pousse vers <branche>"`
+10. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] Les changements sont pousses avec succes
+- [ ] Pas de conflits de merge
+- [ ] Le pipeline CI/CD passe
+- [ ] La branche est a jour
+
+## Notes
+
+Toujours pull avant push pour eviter les conflits. Si la CI echoue, corriger immediatement - ne pas laisser le build casse.

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

@@ -0,0 +1,32 @@
+# Git Tag
+
+## Role
+
+Create a version tag for the release. Follow semantic versioning.
+
+## Actions
+
+1. Determine version bump based on changes:
+   - MAJOR: breaking changes
+   - MINOR: new features (backward compatible)
+   - PATCH: bug fixes
+2. Check current version: `git describe --tags --abbrev=0`
+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. If out of scope work detected: `autocode new "<title>" "<description>" -p P2 -l "<labels>" -a "<criteria>" -s patch`
+7. Document: `autocode comment <key> "Tagged: v<version>"`
+8. Advance: `autocode next <key>`
+
+> Or return: `autocode move <key> <column>`
+
+## Validation Criteria
+
+- [ ] Version follows semver
+- [ ] Tag is annotated with message
+- [ ] Tag pushed to remote
+- [ ] Version increment is appropriate
+
+## Notes
+
+Semantic versioning: MAJOR.MINOR.PATCH. Be conservative - when in doubt, use PATCH. Breaking changes require MAJOR bump.

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

@@ -0,0 +1,32 @@
+# Git Tag
+
+## Role
+
+Creer un tag de version pour la release. Suivre le versionnement semantique.
+
+## Actions
+
+1. Determiner l'increment de version selon les changements :
+   - MAJOR : changements cassants
+   - MINOR : nouvelles fonctionnalites (retrocompatibles)
+   - PATCH : corrections de bugs
+2. Verifier la version actuelle : `git describe --tags --abbrev=0`
+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. Si travail hors scope detecte : `autocode new "<titre>" "<description>" -p P2 -l "<labels>" -a "<criteres>" -s patch`
+7. Documenter : `autocode comment <key> "Tag cree : v<version>"`
+8. Avancer : `autocode next <key>`
+
+> Ou retour : `autocode move <key> <column>`
+
+## Criteres de Validation
+
+- [ ] La version suit semver
+- [ ] Le tag est annote avec un message
+- [ ] Le tag est pousse sur le distant
+- [ ] L'increment de version est approprie
+
+## Notes
+
+Versionnement semantique : MAJOR.MINOR.PATCH. Etre conservateur - en cas de doute, utiliser PATCH. Les changements cassants necessitent un bump MAJOR.

package/templates/{columns/02_in-progress.en.md → prompts/in-progress.en.md}

@@ -12,7 +12,7 @@ Active development. Ticket is being worked on, code is being written.
 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/02_in-progress.fr.md → prompts/in-progress.fr.md}

@@ -12,7 +12,7 @@ Developpement actif. Le ticket est en cours de travail, le code est en cours d'e
 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>`