CI Standards
Inline skill providing CI/CD standards knowledge from the governance documentation. Used by swe-*-dev agents to set up new projects correctly and by ci-checker/ci-fixer agents to validate compliance.
Reference Documents
Mandatory Nx Targets Per App Type
| App Type |
Required Targets |
| Demo-be backend |
codegen, typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |
| Demo-fe frontend |
codegen, typecheck, lint, build, test:unit, test:quick, spec-coverage |
| Fullstack app |
codegen, typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |
| CLI app (Go) |
typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |
| Content platform |
typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |
| Library |
lint, build, test:unit, test:quick |
| E2E runner |
lint, test:e2e, test:e2e:ui, spec-coverage |
Coverage Thresholds
| Threshold |
Projects |
| 90% |
Demo-be backends, CLI apps, Go libs, TS backend (ts-effect) |
| 75% |
Fullstack (crud-fs-ts-nextjs) |
| 70% |
FE apps, crud-fe-ts-nextjs, Dart FE |
Docker Setup Requirements
Every app with a dev or test:integration target must have:
infra/dev/{app}/docker-compose.yml — Dev environmentinfra/dev/{app}/docker-compose.ci.yml — CI overlay (backends only)infra/dev/{app}/.env.example — Environment variable templateapps/{app}/docker-compose.integration.yml — Integration tests (backends only)
E2E Pairing Rules
| Variant Type |
Pairs With |
| Backend (crud-be-*) |
Default frontend (crud-fe-ts-nextjs) |
| Frontend (crud-fe-*) |
Default backend (crud-be-golang-gin) |
| Fullstack (crud-fs-*) |
Self-contained |
Gherkin Consumption Mandate
All testable projects must consume Gherkin specs at ALL test levels. Unit tests are a superset of Gherkin — they MUST implement ALL Gherkin scenarios plus additional non-Gherkin tests.
Workflow Requirements
Each demo backend/frontend must have a per-variant test workflow (test-{app-name}.yml) calling reusable workflows with CRON schedule (2x daily at WIB 06:00 and 18:00).
1---2name: ci-standards3description: CI/CD standards knowledge for validating project compliance with CI conventions4---56# CI Standards78Inline skill providing CI/CD standards knowledge from the governance documentation. Used by `swe-*-dev` agents to set up new projects correctly and by `ci-checker`/`ci-fixer` agents to validate compliance.910## Reference Documents1112- [CI/CD Conventions](../../../repo-governance/development/infra/ci-conventions.md) — Central CI conventions reference13- [Three-Level Testing Standard](../../../repo-governance/development/quality/three-level-testing-standard.md) — Test level definitions14- [Nx Target Standards](../../../repo-governance/development/infra/nx-targets.md) — Mandatory targets per project type15- [Specs Directory Structure Convention](../../../repo-governance/conventions/structure/specs-directory-structure.md) — Canonical path patterns for specs/ directory1617## Mandatory Nx Targets Per App Type1819| App Type | Required Targets |20| ---------------- | --------------------------------------------------------------------------------------- |21| Demo-be backend | codegen, typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |22| Demo-fe frontend | codegen, typecheck, lint, build, test:unit, test:quick, spec-coverage |23| Fullstack app | codegen, typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |24| CLI app (Go) | typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |25| Content platform | typecheck, lint, build, test:unit, test:quick, test:integration, spec-coverage |26| Library | lint, build, test:unit, test:quick |27| E2E runner | lint, test:e2e, test:e2e:ui, spec-coverage |2829## Coverage Thresholds3031| Threshold | Projects |32| --------- | ----------------------------------------------------------- |33| 90% | Demo-be backends, CLI apps, Go libs, TS backend (ts-effect) |34| 75% | Fullstack (crud-fs-ts-nextjs) |35| 70% | FE apps, crud-fe-ts-nextjs, Dart FE |3637## Docker Setup Requirements3839Every app with a `dev` or `test:integration` target must have:4041- `infra/dev/{app}/docker-compose.yml` — Dev environment42- `infra/dev/{app}/docker-compose.ci.yml` — CI overlay (backends only)43- `infra/dev/{app}/.env.example` — Environment variable template44- `apps/{app}/docker-compose.integration.yml` — Integration tests (backends only)4546## E2E Pairing Rules4748| Variant Type | Pairs With |49| ---------------------- | ------------------------------------ |50| Backend (crud-be-\*) | Default frontend (crud-fe-ts-nextjs) |51| Frontend (crud-fe-\*) | Default backend (crud-be-golang-gin) |52| Fullstack (crud-fs-\*) | Self-contained |5354## Gherkin Consumption Mandate5556All testable projects must consume Gherkin specs at ALL test levels. Unit tests are a superset of Gherkin — they MUST implement ALL Gherkin scenarios plus additional non-Gherkin tests.5758## Workflow Requirements5960Each demo backend/frontend must have a per-variant test workflow (`test-{app-name}.yml`) calling reusable workflows with CRON schedule (2x daily at WIB 06:00 and 18:00).
aibot88