GitLab CI Integration (workflow)

Name: test-ci-gitlab-ci
Rating: 87
Author: willyu1007

Operating mode (token-efficient)

•Treat this skill as a router + governor.
•Do not load multiple procedures. Select exactly one procedure below and follow the chosen procedure end-to-end.

Task	Open this procedure	Optional templates
Enable/adjust test jobs (web/api/mobile/perf)	`reference/procedures/enable-test-jobs.md`	`reference/templates/gitlab-ci/`
Standardize artifacts + reporting	`reference/procedures/artifacts-and-reporting.md`	—
Troubleshoot CI failures	`reference/procedures/troubleshoot.md`	—

•
Test command contract
- •
  Each suite must have a single deterministic command runnable in CI:
  - •API (Newman): pnpm test:api
  - •Web (Playwright): pnpm test:e2e:playwright
  - •Web (Cypress): pnpm test:e2e:cypress
  - •Perf (k6): pnpm test:perf:k6 or direct runner (k6 run ... / docker run grafana/k6 ...)
  - •Mobile: pnpm test:mobile:<detox|maestro|appium>
- •
  Commands must:
  - •exit non-zero on test failures
  - •write artifacts to artifacts/<suite>/
•
Artifacts are mandatory
- •Always upload artifacts even on failure: artifacts/ or artifacts/<suite>/
- •Keep artifacts size-bounded (videos/traces on failure only when possible).
•
Secrets management
- •Use GitLab CI variables (masked/protected).
- •Never echo secrets in logs.
•
Gating policy
- •MR gating should run only fast, stable suites.
- •Heavy suites (mobile, load/stress) should be scheduled or manually triggered.

•Whether .gitlab-ci.yml already exists and how the file is structured (includes, stages)
•Which suites are MR-gated vs scheduled
•Required CI variables and how they map to env vars
•Runner constraints (Docker executor, macOS runners for iOS, etc.)

•
If you changed skills:
- •node .ai/scripts/lint-skills.mjs --strict
- •node .ai/skills/testing/test-ci-gitlab-ci/scripts/validate-skill.mjs
•
If you changed .gitlab-ci.yml:
- •
  Trigger a pipeline and confirm:
  - •correct suite execution
  - •artifacts retained
  - •failures show clear signals