nextstage-brasil/skills

ns-gitlab-ci-generator

(NS) Generate and adapt .gitlab-ci.yml for SaaS products with backend and frontend — test, build, E2E gate, deploy by branch.

First seen Jul 25, 2026

Installation

$ npx skills add nextstage-brasil/skills --skill ns-gitlab-ci-generator

Summary

  • (NS) Generate and adapt .gitlab-ci.yml for SaaS products with backend and frontend — test, build, E2E gate, deploy by branch.
  • Use when the user asks for GitLab CI, pipeline setup, or CI/CD bootstrap for a monorepo product.
  • Uses references/templates/gitlab-ci.template.yml as baseline.
  • Out of scope for pure agent-runtime repos without backend+frontend layout.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from nextstage-brasil/skills · top by installs.

npx skills add nextstage-brasil/skills

Browse all from nextstage-brasil/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
LicenseApache-2.0
More metadata
author
nextstage-brasil
version
1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,757 B
  • docs SUMMARY.md 391 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 109 installs

SKILL.md

GitLab CI Generator

Produce .gitlab-ci.yml for backend + frontend SaaS layouts.

Session boot

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

When to use

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

Out of scope

  • agent_runtime-only pipelines
  • Cloud provisioning beyond template contract

Inputs

  • 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 .gitlab-ci.yml

Paths are repo-relative (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 RUNREMOTEE2E=false

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

C — GitLab CI variables

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

  • ENVBACKEND, ENVFRONTEND, test DB vars, RUNREMOTEE2E, 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

  • ns-e2e-tests — E2E folder conventions
  • ns-spec-driven references/e2e-test-task-generator.md — planning E2E scope