메뉴
Use when working with GitLab CI/CD docs: .gitlab-ci.yml syntax, jobs, stages, rules, workflow, include, inputs, components, variables, secrets, runners, executors, pipelines, artifacts, cache, environments, deployments, Docker, services, test reports, and pipeline troubleshooting.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when answering questions about Claude Code CLI features, configuration, hooks, skills, MCP, permissions, settings, sub-agents, teams, plugins, keybindings, IDE integration, CI/CD setup, troubleshooting, or any Claude Code usage topic.
Use when working with Apache Doris: table design, data models (Duplicate/Unique/Aggregate), partitioning, bucketing, SQL syntax, data import (Stream Load, Broker Load, INSERT INTO), data export, lakehouse (Hive/Iceberg/Hudi/Paimon catalogs), materialized views, query acceleration, inverted index, compute-storage decoupled mode, administration, or Doris ecosystem tools.
justfile (just) documentation — a command runner with make-inspired syntax. Covers recipes (parameters, dependencies, shebang/script recipes), justfile language (settings, strings, functions, constants, attributes, conditionals, backticks), modules/imports, variables, shell configuration, and CLI options. USE THIS SKILL WHEN the user asks about just, justfile syntax, just recipes, just modules, just functions, or just settings.
USE THIS SKILL WHEN working with Mastra (TypeScript AI agent framework): building agents, workflows, RAG pipelines, memory, voice, evals, MCP tools, observability/tracing, deploying to Mastra Cloud/Cloudflare/Vercel, or using Mastra client SDK. Triggers on: mastra, Mastra agent, Mastra workflow, createAgent, createWorkflow, mastra.run, MastraClient, @mastra/core.
Use when working with the OpenRouter API: model routing, provider selection, model variants (free/nitro/thinking), tool calling, structured outputs, prompt caching, OAuth, API keys, rate limits, streaming, embeddings, Claude Code integration, or any OpenRouter-specific feature.
Use when working with Ultralytics YOLO, including YOLO26/YOLO11/YOLOv8 models, detect/segment/classify/pose/OBB tasks, train/val/predict/export/track/benchmark modes, dataset YAML formats, HUB/platform workflows, integrations, solutions, or ultralytics Python API behavior.
| name | gitlab-ci-docs |
| description | Use when working with GitLab CI/CD docs: .gitlab-ci.yml syntax, jobs, stages, rules, workflow, include, inputs, components, variables, secrets, runners, executors, pipelines, artifacts, cache, environments, deployments, Docker, services, test reports, and pipeline troubleshooting. |
Official GitLab CI/CD documentation synced from gitlab-org/gitlab/doc/ci.
Use this skill for GitLab CI/CD pipeline configuration and behavior. For project/group user workflows use gitlab-user-docs; for REST/GraphQL API endpoints use gitlab-api-docs; for self-managed instance administration use gitlab-admin-docs; for glab CLI commands use glab-docs / glab-cli.
References are Markdown files under references/:
references/_index.md — GitLab CI/CD overview and getting started.references/yaml/ — .gitlab-ci.yml keyword reference, rules, workflow, include, needs, parallel, matrix, inputs, expressions.references/pipelines/, references/jobs/ — pipeline types, DAGs, scheduled/triggered pipelines, job control, job logs, job artifacts.references/runners/ — GitLab Runner usage from GitLab docs, runner creation/registration, hosted runners, runner scopes.references/variables/, references/secrets/ — CI/CD variables, masked/protected variables, external secrets, ID tokens.references/components/, references/inputs/, references/templates/ — reusable CI/CD components, pipeline inputs, templates.references/docker/, references/services/, references/cloud_deployment/, references/environments/ — containerized jobs, service containers, deployments and environments.references/testing/, references/caching/, references/pipeline_security/, references/debugging.md — test reports, cache, security and troubleshooting.references/ before answering specific GitLab CI/CD behavior or YAML syntax questions..gitlab-ci.yml syntax, defaults, merge behavior, or version constraints.rules behavior, or pipeline source names without checking references.rg -n "^#|rules:|workflow:|include:|needs:|parallel:|matrix|inputs|extends|default:|spec:" skills/gitlab-ci-docs/references/yaml skills/gitlab-ci-docs/references/inputs
rg -n "predefined variable|CI_PIPELINE_SOURCE|CI_COMMIT|masked|protected|hidden|file variable|dotenv" skills/gitlab-ci-docs/references/variables skills/gitlab-ci-docs/references
rg -n "runner|executor|register|tag|hosted runner|instance runner|group runner|project runner" skills/gitlab-ci-docs/references/runners skills/gitlab-ci-docs/references
rg -n "artifact|cache|dependency|needs|DAG|child pipeline|multi-project|schedule|trigger" skills/gitlab-ci-docs/references
rg -n "Docker|service|image:|services:|Kubernetes|environment|deployment|review app" skills/gitlab-ci-docs/references/docker skills/gitlab-ci-docs/references/services skills/gitlab-ci-docs/references/environments
rg -n "Tier:|Offering:|Status:|Introduced|Deprecated|Removed" skills/gitlab-ci-docs/references
gitlab-api-docs or gitlab-admin-docs.