@autocode-cli/autocode 0.1.21 → 0.1.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/templates/prompts/splitter.en.md +1 -1
  3. package/templates/prompts/splitter.fr.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@autocode-cli/autocode",
3
- "version": "0.1.21",
3
+ "version": "0.1.22",
4
4
  "description": "Filesystem-based issues system with web dashboard",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
package/templates/prompts/splitter.en.md CHANGED
@@ -18,7 +18,7 @@ If the task is small enough to be completed in one go, proceed directly without
18
18
  2. Identify natural boundaries between features, layers, or responsibilities
19
19
  3. Define clear acceptance criteria for each sub-issue
20
20
  4. Ensure each split issue is independently testable and deployable
21
- 5. Create sub-issues: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
21
+ 5. Create sub-issues: `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog --parent <issue-key>`
22
22
  6. Verify no functionality has been forgotten or duplicated across issues
23
23
  7. Create an integration issue that references all sub-issues to validate cohesion
24
24
  8. Document: `autocode comment <issue-key> "[summary]"`
package/templates/prompts/splitter.fr.md CHANGED
@@ -18,7 +18,7 @@ Si la tâche est suffisamment petite pour être complétée en une fois, procéd
18
18
  2. Identifier les frontières naturelles entre fonctionnalités, couches ou responsabilités
19
19
  3. Définir des critères d'acceptation clairs pour chaque sous-ticket
20
20
  4. S'assurer que chaque ticket découpé est testable et déployable indépendamment
21
- 5. Créer les sous-tickets : `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
21
+ 5. Créer les sous-tickets : `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog --parent <issue-key>`
22
22
  6. Vérifier qu'aucune fonctionnalité n'a été oubliée ou dupliquée entre les tickets
23
23
  7. Créer un ticket d'intégration qui référence tous les sous-tickets pour valider la cohésion
24
24
  8. Documenter : `autocode comment <issue-key> "[résumé]"`