Run any Skill in Manus with one click

$pwd:

gitlab-ci

Name: Gitlab Ci
Author: willyu1007

// GitLab CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

Run Skill in Manus

$ git log --oneline --stat

stars:0

forks:0

updated:February 10, 2026 at 01:16

File Explorer

7 files

SKILL.md

readonly

name	gitlab-ci
description	GitLab CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitLab CI Integration (workflow)

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.

Routing (pick one procedure)

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`	—

Shared non-negotiables (apply to all procedures)

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.

Minimal inputs before changing CI

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.)

Verification

If you changed skills:
- node .ai/scripts/lint-skills.mjs --strict
- node .ai/skills/features/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

Boundaries

Do not hardcode secrets or base URLs in .gitlab-ci.yml.
Do not make MR gating flaky; move unstable suites to scheduled runs.

related-skills.json

same repository

apply-frontend-common-patterns.md

from "willyu1007/The-UniAssist-Entrance-App"

Apply local React patterns (derived state, memoization, callback stability, controlled inputs) to improve predictability and render efficiency inside components. Primary intent: component-internal logic quality and render behavior; complements but does not replace routing/data/styling skills.

2026-02-100

apply-frontend-ui-guidelines.md

from "willyu1007/The-UniAssist-Entrance-App"

Orchestrate end-to-end frontend feature implementation across components, hooks, routing, data fetching, styling, and user-visible states with consistent architecture and verification. Primary intent: cross-cutting implementation alignment; pairs with specialized skills when one concern needs deeper treatment.

2026-02-100

build-react-components.md

from "willyu1007/The-UniAssist-Entrance-App"

Build or refactor React components with typed props, clear composition, and explicit interaction/loading/empty/error behavior. Primary intent: component contract and behavior correctness; pairs with styling or design-direction skills for visual decisions.

2026-02-100

frontend-design.md

from "willyu1007/The-UniAssist-Entrance-App"

Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.

2026-02-100

style-frontend-ui.md

from "willyu1007/The-UniAssist-Entrance-App"

Implement and normalize UI styling within an existing design system using theme tokens, reusable style primitives, responsive rules, and accessibility checks. Primary intent: styling execution consistency; can follow frontend-design when a creative direction needs maintainable implementation.

2026-02-100

handle-frontend-loading-and-errors.md

from "willyu1007/The-UniAssist-Entrance-App"

Implement resilient loading/empty/error/permission/retry UX states for async interfaces with user-safe messaging and recoverable flows. Primary intent: failure-state UX quality; pairs with component, data-fetching, and UI-guideline skills when needed.

2026-02-100

package.json

"author": "willyu1007"

"repository": "willyu1007/The-UniAssist-Entrance-App"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

GitLab CI Integration (workflow)

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.

Routing (pick one procedure)

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

—

Shared non-negotiables (apply to all procedures)

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.

Minimal inputs before changing CI

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.)

Verification

If you changed skills:

node .ai/scripts/lint-skills.mjs --strict
node .ai/skills/features/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

Boundaries

Do not hardcode secrets or base URLs in .gitlab-ci.yml.

Do not make MR gating flaky; move unstable suites to scheduled runs.

gitlab-ci

GitLab CI Integration (workflow)

Operating mode (token-efficient)

Routing (pick one procedure)

Shared non-negotiables (apply to all procedures)

Minimal inputs before changing CI

Verification

Boundaries

More from this repository

More from this repository

GitLab CI Integration (workflow)

Operating mode (token-efficient)

Routing (pick one procedure)

Shared non-negotiables (apply to all procedures)

Minimal inputs before changing CI

Verification

Boundaries