원클릭으로 Manus에서 모든 스킬 실행

$pwd:

test-ci-gitlab-ci

Name: Test Ci Gitlab Ci
Author: willyu1007

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

Manus에서 실행

$ git log --oneline --stat

stars:0

forks:0

updated:2026년 2월 6일 12:41

파일 탐색기

6 개 파일

SKILL.md

readonly

name	test-ci-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/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

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

같은 저장소

initialize-project-from-requirements.md

from "willyu1007/Template-Skill-Basic"

Use only in repos that still include the `init/` bootstrap kit to produce Stage A/B/C artifacts, update skill pack selection, and sync provider skill wrappers.

2026-02-270

plan-maker.md

from "willyu1007/Template-Skill-Basic"

Create a goal-aligned macro-level roadmap artifact (dev-docs/active/<task>/roadmap.md) by asking clarifying questions and recording assumptions; planning only (no code changes).

2026-02-080

agent-builder.md

from "willyu1007/Template-Skill-Basic"

Build a complete, production-embedded Agent module for a real feature request (API + optional worker/sdk/cron/pipeline), including blueprint, scaffolded runtime, prompt pack, docs, and registry entry. Enforces explicit user approvals, no-secrets-in-repo, fixed API route names (run/health), and conversation/memory strategy decisions.

2026-02-070

llm-engineering.md

from "willyu1007/Template-Skill-Basic"

Entry workflow for LLM engineering tasks (provider integration, calling wrapper, routing profiles, prompt templates, cost/telemetry, credentials/config keys). Routes to one procedure and enforces required verification.

2026-02-070

project-status-reporter.md

from "willyu1007/Template-Skill-Basic"

Read-only progress reporter. Produces a structured status snapshot from existing project/task artifacts (project hub + dev-docs) and includes an actionable next command; never modifies repo files.

2026-02-070

frontend-design.md

from "willyu1007/Template-Skill-Basic"

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-070

package.json

"author": "willyu1007"

"repository": "willyu1007/Template-Skill-Basic"

GitHub 저장소 열기 Creator 저장소 보기

$ install --global

$ download --local

Manus에서 실행

$ useful --forSOC

소프트웨어 품질 보증 분석가·테스터컴퓨터 및 수학직15-1253L4

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/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

Boundaries

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

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

test-ci-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

이 저장소의 다른 Skills

이 저장소의 다른 Skills

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