gitlab-ci-generator

Name: gitlab-ci-generator
Author: nextstage-brasil

github.com/nextstage-brasilCloud & DevOps046 installsUpdated 5d ago

About gitlab-ci-generator

A skill for generating and adapting `.gitlab-ci.yml` pipelines for backend-and-frontend SaaS products. It uses a supplied template, checks repository-specific paths and commands, documents CI variable names, and validates the resulting YAML and job layout.

Key features

01Copy a baseline pipeline template
02Adapt paths, images, and test commands
03Configure branch-based deployment rules
04Document CI variable names
05Lint YAML and check job layout

Use cases

01Set up CI for a backend-and-frontend SaaS
02Adjust pipelines for repository folder layouts
03Align test and build jobs with project manifests
04Check pipeline configuration before use

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nextstage-brasil/skills --skill gitlab-ci-generator

After installing, type/gitlab-ci-generatorin Claude Code to confirm it loaded.

Bundled filesevals/evals.jsonreferences/templates/gitlab-ci.template.yml

Details

From the project README

GitLab CI Generator

Produce {product_root}/.gitlab-ci.yml for backend + frontend SaaS layouts.

Harness discovery

Load {harness}/rules/infra-rules.mdc, backend-tests-rules.mdc, e2e-tests-rules.mdc when present. Read {product_root}/docker-compose.yml.

When to use

Create or adjust .gitlab-ci.yml
product_class saas or intelligent_saas (backend + frontend required)
Branch-based test/build/deploy

Out of scope

agent_runtime-only pipelines
Cloud provisioning beyond template contract

Inputs

{product_root} confirmed
Target branches (minimum: develop, homolog, main)
E2E folder name (testes-cypress, tests-e2e, or frontend/cypress)

Workflow

A — Copy baseline

Copy references/templates/gitlab-ci.template.yml to {product_root}/.gitlab-ci.yml

For separate product repos: paths are relative to product root (backend/, frontend/).

B — Mandatory adaptations

Item	Action
E2E folder	Match product folder in `changes:` and job `cd`
PHP image	Align to backend Dockerfile
Test commands	Match `composer.json` / `package.json`
Lockfile	`yarn.lock` vs `package-lock.json` in cache key
Deploy branches	Adjust regex if not main/homolog/develop
E2E disabled	Remove e2e jobs from deploy `needs` or document `RUN_REMOTE_E2E=false`

Do not copy another product's CI file — use this template only.

C — GitLab CI variables

Document in optional {product_root}/docs/context/ci-cd-notes.md:

ENV_BACKEND, ENV_FRONTEND, test DB vars, RUN_REMOTE_E2E, GCP keys — names only, no secret values

D — Validate

Lint YAML; confirm jobs match repo layout.

References

File	When
`references/templates/gitlab-ci.template.yml`	Baseline pipeline

Related skills

code-e2e-tests — E2E folder conventions
pm-e2e-test-generator — planning E2E scope

Comments

Markdown supported

Details

Author: nextstage-brasil
Repository: nextstage-brasil/skills
Category: Cloud & DevOps
Installs: 46
GitHub stars: 0

Report

More skills

All skills

lark-apps

open.feishu.cn

739.5k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

wizard

github.com/mattpocock

576.6k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-prepare

github.com/microsoft

573.4k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

azure-ai

github.com/microsoft

572.8k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.