ci-standards
CI/CD standards knowledge for validating project compliance with CI conventions
Best use case
ci-standards is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
CI/CD standards knowledge for validating project compliance with CI conventions
Teams using ci-standards should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ci-standards/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ci-standards Compares
| Feature / Agent | ci-standards | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
CI/CD standards knowledge for validating project compliance with CI conventions
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# CI Standards
Inline skill providing CI/CD standards knowledge from the governance documentation. Used by `ci-checker` and `ci-fixer` agents to validate compliance.
## Reference Documents
- [CI/CD Conventions](../../../repo-governance/development/infra/ci-conventions.md) — Central CI conventions reference
- [Three-Level Testing Standard](../../../repo-governance/development/quality/three-level-testing-standard.md) — Test level definitions
- [Nx Target Standards](../../../repo-governance/development/infra/nx-targets.md) — Mandatory targets per project type
- [Specs Directory Structure Convention](../../../repo-governance/conventions/structure/specs-directory-structure.md) — Canonical path patterns for specs/ directory
## 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% | organiclever-be, CLI apps, Go libs |
| 80% | Content platforms (ayokoding-web, ose-web) |
| 70% | organiclever-web |
## Docker Setup Requirements
Every app with a `dev` or `test:integration` target must have:
- `infra/dev/{app}/docker-compose.yml` — Dev environment
- `infra/dev/{app}/docker-compose.ci.yml` — CI overlay (backends only)
- `infra/dev/{app}/.env.example` — Environment variable template
- `apps/{app}/docker-compose.integration.yml` — Integration tests (backends only)
## E2E Pairing Rules
| Variant Type | Pairs With |
| ------------ | ------------------------------- |
| Backend | Corresponding frontend via E2E |
| Frontend | Corresponding backend via E2E |
| Fullstack | Self-contained (own API routes) |
## 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).Related Skills
nx-workspace
Explore and understand Nx workspaces. USE WHEN answering questions about the workspace, projects, or tasks. ALSO USE WHEN an nx command fails or you need to check available targets/configuration before running a task. EXAMPLES: 'What projects are in this workspace?', 'How is project X configured?', 'What depends on library Y?', 'What targets can I run?', 'Cannot find configuration for task', 'debug nx task failure'.
nx-run-tasks
Helps with running tasks in an Nx workspace. USE WHEN the user wants to execute build, test, lint, serve, or run any other tasks defined in the workspace.
nx-plugins
Find and add Nx plugins. USE WHEN user wants to discover available plugins, install a new plugin, or add support for a specific framework or technology to the workspace.
nx-import
Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.
nx-generate
Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
monitor-ci
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, glab, etc.) for CI monitoring — it integrates with Nx Cloud self-healing which those tools cannot access.
link-workspace-packages
Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager's workspace commands to fix actual linking.
swe-programming-typescript
TypeScript coding standards from authoritative docs/explanation/software-engineering/programming-languages/typescript/ documentation
swe-programming-rust
Rust coding standards from authoritative docs/explanation/software-engineering/programming-languages/rust/ documentation
swe-programming-golang
Go coding standards from authoritative docs/explanation/software-engineering/programming-languages/golang/ documentation
swe-programming-fsharp
F# coding standards from authoritative docs/explanation/software-engineering/programming-languages/f-sharp/ documentation
swe-programming-csharp
C# coding standards from authoritative docs/explanation/software-engineering/programming-languages/c-sharp/ documentation