@autocode-cli/autocode 0.1.13 → 0.1.14
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.
- package/dist/server/api.d.ts.map +1 -1
- package/dist/server/api.js +95 -1
- package/dist/server/api.js.map +1 -1
- package/dist/server/dashboard/pages/autocreate.d.ts +9 -0
- package/dist/server/dashboard/pages/autocreate.d.ts.map +1 -0
- package/dist/server/dashboard/pages/autocreate.js +847 -0
- package/dist/server/dashboard/pages/autocreate.js.map +1 -0
- package/dist/server/dashboard/pages/index.d.ts +1 -0
- package/dist/server/dashboard/pages/index.d.ts.map +1 -1
- package/dist/server/dashboard/pages/index.js +1 -0
- package/dist/server/dashboard/pages/index.js.map +1 -1
- package/dist/server/dashboard/pages/pipeline-configurator.d.ts.map +1 -1
- package/dist/server/dashboard/pages/pipeline-configurator.js +22 -0
- package/dist/server/dashboard/pages/pipeline-configurator.js.map +1 -1
- package/dist/server/dashboard.d.ts +1 -1
- package/dist/server/dashboard.d.ts.map +1 -1
- package/dist/server/dashboard.js +1 -1
- package/dist/server/dashboard.js.map +1 -1
- package/dist/server/index.d.ts.map +1 -1
- package/dist/server/index.js +9 -1
- package/dist/server/index.js.map +1 -1
- package/dist/services/autocreate.d.ts +34 -0
- package/dist/services/autocreate.d.ts.map +1 -0
- package/dist/services/autocreate.js +503 -0
- package/dist/services/autocreate.js.map +1 -0
- package/dist/types/index.d.ts +49 -0
- package/dist/types/index.d.ts.map +1 -1
- package/package.json +1 -1
- package/templates/catalog.yaml +102 -0
- package/templates/prompts/accessibility-check.en.md +25 -0
- package/templates/prompts/accessibility-check.fr.md +25 -0
- package/templates/prompts/api-endpoints-test.en.md +26 -0
- package/templates/prompts/api-endpoints-test.fr.md +26 -0
- package/templates/prompts/build-dist.en.md +20 -0
- package/templates/prompts/build-dist.fr.md +20 -0
- package/templates/prompts/ci-gitlab-validate.en.md +22 -0
- package/templates/prompts/ci-gitlab-validate.fr.md +22 -0
- package/templates/prompts/claude-integration-test.en.md +22 -0
- package/templates/prompts/claude-integration-test.fr.md +22 -0
- package/templates/prompts/cli-smoke-test.en.md +30 -0
- package/templates/prompts/cli-smoke-test.fr.md +30 -0
- package/templates/prompts/dashboard-responsive.en.md +27 -0
- package/templates/prompts/dashboard-responsive.fr.md +27 -0
- package/templates/prompts/dead-code-check.en.md +25 -0
- package/templates/prompts/dead-code-check.fr.md +25 -0
- package/templates/prompts/deps-licenses.en.md +23 -0
- package/templates/prompts/deps-licenses.fr.md +23 -0
- package/templates/prompts/deps-outdated.en.md +23 -0
- package/templates/prompts/deps-outdated.fr.md +23 -0
- package/templates/prompts/docs-readme-validate.en.md +22 -0
- package/templates/prompts/docs-readme-validate.fr.md +22 -0
- package/templates/prompts/error-handling-review.en.md +24 -0
- package/templates/prompts/error-handling-review.fr.md +24 -0
- package/templates/prompts/esm-compatibility.en.md +24 -0
- package/templates/prompts/esm-compatibility.fr.md +24 -0
- package/templates/prompts/file-watcher-test.en.md +20 -0
- package/templates/prompts/file-watcher-test.fr.md +20 -0
- package/templates/prompts/format-prettier-setup.en.md +21 -0
- package/templates/prompts/format-prettier-setup.fr.md +21 -0
- package/templates/prompts/git-conventional-commits.en.md +21 -0
- package/templates/prompts/git-conventional-commits.fr.md +21 -0
- package/templates/prompts/git-hooks-setup.en.md +27 -0
- package/templates/prompts/git-hooks-setup.fr.md +27 -0
- package/templates/prompts/graceful-shutdown.en.md +25 -0
- package/templates/prompts/graceful-shutdown.fr.md +25 -0
- package/templates/prompts/i18n-completeness.en.md +21 -0
- package/templates/prompts/i18n-completeness.fr.md +21 -0
- package/templates/prompts/landing-html-validate.en.md +23 -0
- package/templates/prompts/landing-html-validate.fr.md +23 -0
- package/templates/prompts/lint-eslint-setup.en.md +20 -0
- package/templates/prompts/lint-eslint-setup.fr.md +20 -0
- package/templates/prompts/node-version-check.en.md +21 -0
- package/templates/prompts/node-version-check.fr.md +21 -0
- package/templates/prompts/npm-publish-dry-run.en.md +25 -0
- package/templates/prompts/npm-publish-dry-run.fr.md +25 -0
- package/templates/prompts/pkg-exports-validate.en.md +23 -0
- package/templates/prompts/pkg-exports-validate.fr.md +23 -0
- package/templates/prompts/port-conflict-handling.en.md +22 -0
- package/templates/prompts/port-conflict-handling.fr.md +22 -0
- package/templates/prompts/security-audit.en.md +20 -0
- package/templates/prompts/security-audit.fr.md +20 -0
- package/templates/prompts/security-secrets.en.md +26 -0
- package/templates/prompts/security-secrets.fr.md +26 -0
- package/templates/prompts/template-validation.en.md +23 -0
- package/templates/prompts/template-validation.fr.md +23 -0
- package/templates/prompts/testing-coverage.en.md +20 -0
- package/templates/prompts/testing-coverage.fr.md +20 -0
- package/templates/prompts/testing-vitest.en.md +17 -0
- package/templates/prompts/testing-vitest.fr.md +17 -0
- package/templates/prompts/typecheck.en.md +17 -0
- package/templates/prompts/typecheck.fr.md +17 -0
- package/templates/prompts/version-semver.en.md +20 -0
- package/templates/prompts/version-semver.fr.md +20 -0
- package/templates/prompts/websocket-test.en.md +19 -0
- package/templates/prompts/websocket-test.fr.md +19 -0
- package/templates/prompts/yaml-validate.en.md +24 -0
- package/templates/prompts/yaml-validate.fr.md +24 -0
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# npm Security Audit
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Check for security vulnerabilities in project dependencies.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Run `npm audit` to list vulnerabilities
|
|
8
|
+
2. Analyze severity level (low, moderate, high, critical)
|
|
9
|
+
3. For critical/high vulnerabilities, run `npm audit fix`
|
|
10
|
+
4. If vulnerabilities persist, evaluate:
|
|
11
|
+
- Manual dependency update
|
|
12
|
+
- Replacement with alternative
|
|
13
|
+
- Risk acceptance with justification
|
|
14
|
+
5. Document accepted vulnerabilities
|
|
15
|
+
|
|
16
|
+
## Validation Criteria
|
|
17
|
+
- [ ] `npm audit` executed
|
|
18
|
+
- [ ] No critical vulnerabilities
|
|
19
|
+
- [ ] No unaddressed high vulnerabilities
|
|
20
|
+
- [ ] Accepted vulnerabilities documented
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Audit de sécurité npm
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Vérifier les vulnérabilités de sécurité dans les dépendances du projet.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Exécuter `npm audit` pour lister les vulnérabilités
|
|
8
|
+
2. Analyser le niveau de sévérité (low, moderate, high, critical)
|
|
9
|
+
3. Pour les vulnérabilités critiques/high, exécuter `npm audit fix`
|
|
10
|
+
4. Si des vulnérabilités persistent, évaluer:
|
|
11
|
+
- Mise à jour manuelle de la dépendance
|
|
12
|
+
- Remplacement par une alternative
|
|
13
|
+
- Acceptation du risque avec justification
|
|
14
|
+
5. Documenter les vulnérabilités acceptées
|
|
15
|
+
|
|
16
|
+
## Critères de validation
|
|
17
|
+
- [ ] `npm audit` exécuté
|
|
18
|
+
- [ ] Aucune vulnérabilité critique (critical)
|
|
19
|
+
- [ ] Aucune vulnérabilité haute (high) non traitée
|
|
20
|
+
- [ ] Vulnérabilités acceptées documentées
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Secrets Detection
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Verify no secrets or credentials are present in source code.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Install gitleaks if missing:
|
|
8
|
+
```bash
|
|
9
|
+
# or use npx @secretlint/secretlint
|
|
10
|
+
```
|
|
11
|
+
2. Scan repository:
|
|
12
|
+
```bash
|
|
13
|
+
npx @secretlint/secretlint "**/*"
|
|
14
|
+
```
|
|
15
|
+
3. Check sensitive files:
|
|
16
|
+
- .env (must not be committed)
|
|
17
|
+
- Configuration files
|
|
18
|
+
- Templates
|
|
19
|
+
4. Verify .gitignore includes sensitive files
|
|
20
|
+
5. Scan git history if needed
|
|
21
|
+
|
|
22
|
+
## Validation Criteria
|
|
23
|
+
- [ ] No secrets detected in src/
|
|
24
|
+
- [ ] .env in .gitignore
|
|
25
|
+
- [ ] No hardcoded tokens/API keys
|
|
26
|
+
- [ ] Clean git history
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
# Détection des secrets
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Vérifier qu'aucun secret ou credential n'est présent dans le code source.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Installer gitleaks si absent:
|
|
8
|
+
```bash
|
|
9
|
+
# ou utiliser npx @secretlint/secretlint
|
|
10
|
+
```
|
|
11
|
+
2. Scanner le repository:
|
|
12
|
+
```bash
|
|
13
|
+
npx @secretlint/secretlint "**/*"
|
|
14
|
+
```
|
|
15
|
+
3. Vérifier les fichiers sensibles:
|
|
16
|
+
- .env (ne doit pas être commité)
|
|
17
|
+
- Fichiers de configuration
|
|
18
|
+
- Templates
|
|
19
|
+
4. Vérifier .gitignore inclut les fichiers sensibles
|
|
20
|
+
5. Scanner l'historique git si nécessaire
|
|
21
|
+
|
|
22
|
+
## Critères de validation
|
|
23
|
+
- [ ] Aucun secret détecté dans src/
|
|
24
|
+
- [ ] .env dans .gitignore
|
|
25
|
+
- [ ] Pas de tokens/clés API hardcodés
|
|
26
|
+
- [ ] Historique git propre
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Template Validation
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Verify project templates are correct and functional.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. List templates in templates/
|
|
8
|
+
2. For each template:
|
|
9
|
+
- Verify YAML/Markdown syntax
|
|
10
|
+
- Check placeholders
|
|
11
|
+
- Test generation with `autocode init`
|
|
12
|
+
3. Verify generated structure:
|
|
13
|
+
- .autocode/
|
|
14
|
+
- .autocode/tickets/
|
|
15
|
+
- .autocode/config.yml
|
|
16
|
+
- pipeline.yml
|
|
17
|
+
4. Test different configurations
|
|
18
|
+
|
|
19
|
+
## Validation Criteria
|
|
20
|
+
- [ ] All templates parse without errors
|
|
21
|
+
- [ ] `autocode init` generates correct structure
|
|
22
|
+
- [ ] Generated files are valid
|
|
23
|
+
- [ ] No unreplaced placeholders
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Validation des templates
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Vérifier que les templates de projet sont corrects et fonctionnels.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Lister les templates dans templates/
|
|
8
|
+
2. Pour chaque template:
|
|
9
|
+
- Vérifier la syntaxe YAML/Markdown
|
|
10
|
+
- Vérifier les placeholders
|
|
11
|
+
- Tester la génération avec `autocode init`
|
|
12
|
+
3. Vérifier la structure générée:
|
|
13
|
+
- .autocode/
|
|
14
|
+
- .autocode/tickets/
|
|
15
|
+
- .autocode/config.yml
|
|
16
|
+
- pipeline.yml
|
|
17
|
+
4. Tester différentes configurations
|
|
18
|
+
|
|
19
|
+
## Critères de validation
|
|
20
|
+
- [ ] Tous les templates parsent sans erreur
|
|
21
|
+
- [ ] `autocode init` génère la bonne structure
|
|
22
|
+
- [ ] Fichiers générés sont valides
|
|
23
|
+
- [ ] Pas de placeholder non remplacé
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Code Coverage
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Measure and validate code coverage by unit tests.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Run `npx vitest run --coverage`
|
|
8
|
+
2. Analyze generated coverage report
|
|
9
|
+
3. Identify files with insufficient coverage (<80%)
|
|
10
|
+
4. Check coverage of critical modules:
|
|
11
|
+
- src/core/ (ticket.ts, column.ts, workflow.ts)
|
|
12
|
+
- src/server/api.ts
|
|
13
|
+
- src/services/
|
|
14
|
+
5. Add tests for uncovered areas if needed
|
|
15
|
+
|
|
16
|
+
## Validation Criteria
|
|
17
|
+
- [ ] Global coverage >= 70%
|
|
18
|
+
- [ ] Core modules covered at >= 80%
|
|
19
|
+
- [ ] No critical files with 0% coverage
|
|
20
|
+
- [ ] Coverage report generated without errors
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Couverture de code
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Mesurer et valider la couverture de code par les tests unitaires.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Exécuter `npx vitest run --coverage`
|
|
8
|
+
2. Analyser le rapport de couverture généré
|
|
9
|
+
3. Identifier les fichiers avec couverture insuffisante (<80%)
|
|
10
|
+
4. Vérifier la couverture des modules critiques:
|
|
11
|
+
- src/core/ (ticket.ts, column.ts, workflow.ts)
|
|
12
|
+
- src/server/api.ts
|
|
13
|
+
- src/services/
|
|
14
|
+
5. Ajouter des tests pour les zones non couvertes si nécessaire
|
|
15
|
+
|
|
16
|
+
## Critères de validation
|
|
17
|
+
- [ ] Couverture globale >= 70%
|
|
18
|
+
- [ ] Modules core couverts à >= 80%
|
|
19
|
+
- [ ] Aucun fichier critique avec 0% couverture
|
|
20
|
+
- [ ] Rapport de couverture généré sans erreur
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Vitest Unit Tests
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Run unit tests with Vitest and ensure sufficient coverage.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Run `npm run test` or `npx vitest run`
|
|
8
|
+
2. Verify all tests pass
|
|
9
|
+
3. Analyze failed tests if any
|
|
10
|
+
4. Check configuration in vitest.config.ts
|
|
11
|
+
5. Identify modules not covered by tests
|
|
12
|
+
|
|
13
|
+
## Validation Criteria
|
|
14
|
+
- [ ] `npm run test` runs without errors
|
|
15
|
+
- [ ] All tests pass (0 failures)
|
|
16
|
+
- [ ] src/**/*.test.ts files are executed
|
|
17
|
+
- [ ] No regressions introduced
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Tests unitaires Vitest
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Exécuter les tests unitaires avec Vitest et s'assurer que la couverture est suffisante.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Exécuter `npm run test` ou `npx vitest run`
|
|
8
|
+
2. Vérifier que tous les tests passent
|
|
9
|
+
3. Analyser les tests échoués le cas échéant
|
|
10
|
+
4. Vérifier la configuration dans vitest.config.ts
|
|
11
|
+
5. Identifier les modules non couverts par les tests
|
|
12
|
+
|
|
13
|
+
## Critères de validation
|
|
14
|
+
- [ ] `npm run test` s'exécute sans erreur
|
|
15
|
+
- [ ] Tous les tests passent (0 échec)
|
|
16
|
+
- [ ] Les fichiers src/**/*.test.ts sont exécutés
|
|
17
|
+
- [ ] Aucune régression introduite
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# TypeScript Type Checking
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Validate that TypeScript code compiles without errors with strict options enabled (strict, noImplicitAny, strictNullChecks, etc.).
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Run `npx tsc --noEmit` to check types without generating files
|
|
8
|
+
2. Analyze compilation errors if any
|
|
9
|
+
3. Verify tsconfig.json maintains strict options
|
|
10
|
+
4. Identify unjustified `any` usages
|
|
11
|
+
5. Fix detected type errors
|
|
12
|
+
|
|
13
|
+
## Validation Criteria
|
|
14
|
+
- [ ] `npx tsc --noEmit` runs without errors
|
|
15
|
+
- [ ] No implicit `any` in code
|
|
16
|
+
- [ ] All strict options enabled in tsconfig.json
|
|
17
|
+
- [ ] Types properly defined in src/types/
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
# Vérification des types TypeScript
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Valider que le code TypeScript compile sans erreur avec les options strictes activées (strict, noImplicitAny, strictNullChecks, etc.).
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Exécuter `npx tsc --noEmit` pour vérifier les types sans générer de fichiers
|
|
8
|
+
2. Analyser les erreurs de compilation s'il y en a
|
|
9
|
+
3. Vérifier que tsconfig.json maintient les options strictes
|
|
10
|
+
4. Identifier les usages de `any` non justifiés
|
|
11
|
+
5. Corriger les erreurs de types détectées
|
|
12
|
+
|
|
13
|
+
## Critères de validation
|
|
14
|
+
- [ ] `npx tsc --noEmit` s'exécute sans erreur
|
|
15
|
+
- [ ] Aucun `any` implicite dans le code
|
|
16
|
+
- [ ] Toutes les options strictes sont activées dans tsconfig.json
|
|
17
|
+
- [ ] Les types sont correctement définis dans src/types/
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Semantic Versioning
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Validate version follows semver format and is consistent.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Check version in package.json (currently 0.1.13)
|
|
8
|
+
2. Compare with latest git tag: `git describe --tags`
|
|
9
|
+
3. Analyze changes since last version:
|
|
10
|
+
- Breaking changes → MAJOR (x.0.0)
|
|
11
|
+
- New features → MINOR (0.x.0)
|
|
12
|
+
- Bug fixes → PATCH (0.0.x)
|
|
13
|
+
4. Verify consistency with CHANGELOG.md
|
|
14
|
+
5. Use `just new-tag` to create tag if needed
|
|
15
|
+
|
|
16
|
+
## Validation Criteria
|
|
17
|
+
- [ ] package.json version in semver format
|
|
18
|
+
- [ ] Git tag matches version
|
|
19
|
+
- [ ] Bump type consistent with changes
|
|
20
|
+
- [ ] CHANGELOG updated
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Versioning sémantique
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Valider que la version suit le format semver et est cohérente.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Vérifier la version dans package.json (actuellement 0.1.13)
|
|
8
|
+
2. Comparer avec le dernier tag git: `git describe --tags`
|
|
9
|
+
3. Analyser les changements depuis la dernière version:
|
|
10
|
+
- Breaking changes → MAJOR (x.0.0)
|
|
11
|
+
- Nouvelles fonctionnalités → MINOR (0.x.0)
|
|
12
|
+
- Corrections de bugs → PATCH (0.0.x)
|
|
13
|
+
4. Vérifier cohérence avec CHANGELOG.md
|
|
14
|
+
5. Utiliser `just new-tag` pour créer un tag si nécessaire
|
|
15
|
+
|
|
16
|
+
## Critères de validation
|
|
17
|
+
- [ ] Version package.json au format semver
|
|
18
|
+
- [ ] Tag git correspond à la version
|
|
19
|
+
- [ ] Type de bump cohérent avec les changements
|
|
20
|
+
- [ ] CHANGELOG mis à jour
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# WebSocket Test
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Verify WebSocket connection works for real-time updates.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Start server with WebSocket enabled
|
|
8
|
+
2. Connect to WebSocket: `ws://localhost:3456/ws`
|
|
9
|
+
3. Verify connection message received
|
|
10
|
+
4. Create/modify a ticket via API
|
|
11
|
+
5. Verify event received via WebSocket
|
|
12
|
+
6. Test automatic reconnection
|
|
13
|
+
7. Check performance with multiple clients
|
|
14
|
+
|
|
15
|
+
## Validation Criteria
|
|
16
|
+
- [ ] WebSocket connection established
|
|
17
|
+
- [ ] Messages received in real-time
|
|
18
|
+
- [ ] JSON event format correct
|
|
19
|
+
- [ ] No memory leak on multiple connections
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Test WebSocket
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Vérifier que la connexion WebSocket fonctionne pour les mises à jour temps réel.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Démarrer le serveur avec WebSocket activé
|
|
8
|
+
2. Se connecter au WebSocket: `ws://localhost:3456/ws`
|
|
9
|
+
3. Vérifier la réception du message de connexion
|
|
10
|
+
4. Créer/modifier un ticket via l'API
|
|
11
|
+
5. Vérifier que l'événement est reçu via WebSocket
|
|
12
|
+
6. Tester la reconnexion automatique
|
|
13
|
+
7. Vérifier les performances avec plusieurs clients
|
|
14
|
+
|
|
15
|
+
## Critères de validation
|
|
16
|
+
- [ ] Connexion WebSocket établie
|
|
17
|
+
- [ ] Messages reçus en temps réel
|
|
18
|
+
- [ ] Format JSON des événements correct
|
|
19
|
+
- [ ] Pas de fuite mémoire sur connexions multiples
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# YAML Files Validation
|
|
2
|
+
|
|
3
|
+
## Role
|
|
4
|
+
Verify syntax and structure of project YAML files.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Identify all YAML files:
|
|
8
|
+
- pipeline.yml
|
|
9
|
+
- .gitlab-ci.yml
|
|
10
|
+
- .autocode/config.yml (if present)
|
|
11
|
+
- templates/*.yml
|
|
12
|
+
2. Validate each file with yamllint:
|
|
13
|
+
```bash
|
|
14
|
+
npx yaml-lint pipeline.yml
|
|
15
|
+
```
|
|
16
|
+
3. Check indentation (2 spaces)
|
|
17
|
+
4. Check duplicate keys
|
|
18
|
+
5. Validate specific schemas (GitLab CI)
|
|
19
|
+
|
|
20
|
+
## Validation Criteria
|
|
21
|
+
- [ ] All YAML files syntactically valid
|
|
22
|
+
- [ ] Consistent indentation
|
|
23
|
+
- [ ] No duplicate keys
|
|
24
|
+
- [ ] Specific schemas respected
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# Validation des fichiers YAML
|
|
2
|
+
|
|
3
|
+
## Rôle
|
|
4
|
+
Vérifier la syntaxe et la structure des fichiers YAML du projet.
|
|
5
|
+
|
|
6
|
+
## Actions
|
|
7
|
+
1. Identifier tous les fichiers YAML:
|
|
8
|
+
- pipeline.yml
|
|
9
|
+
- .gitlab-ci.yml
|
|
10
|
+
- .autocode/config.yml (si présent)
|
|
11
|
+
- templates/*.yml
|
|
12
|
+
2. Valider chaque fichier avec yamllint:
|
|
13
|
+
```bash
|
|
14
|
+
npx yaml-lint pipeline.yml
|
|
15
|
+
```
|
|
16
|
+
3. Vérifier l'indentation (2 espaces)
|
|
17
|
+
4. Vérifier les clés dupliquées
|
|
18
|
+
5. Valider les schémas spécifiques (GitLab CI)
|
|
19
|
+
|
|
20
|
+
## Critères de validation
|
|
21
|
+
- [ ] Tous les fichiers YAML sont syntaxiquement valides
|
|
22
|
+
- [ ] Indentation cohérente
|
|
23
|
+
- [ ] Pas de clés dupliquées
|
|
24
|
+
- [ ] Schémas spécifiques respectés
|