# GitLab Stack Creator

GitLab Stack Creator scaffolds a new Docker stack project: folders, git settings, validation hooks and docs. Use it when you start a stack in the GitLab stack layout.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 294 installs · ★ 93 repo stars
- Author: rknall
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/rknall/claude-skills/tree/HEAD/stack-creator/SKILL.md
- Updated: 2025-10-20
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/gitlab-stack-creator

## What it does

This skill sets up a new Docker stack project following the GitLab stack layout. It begins by asking for the project name, the services you need, an optional remote repository URL and the environment. It never guesses. If the directory or repo already exists, it asks before touching anything.

The scaffold has `config`, `secrets` (mode `700`), `_temporary`, `scripts` and `docs/decisions`, plus `docker-compose.yml`, `.env.example`, `.gitignore`, `.dockerignore`, `CLAUDE.md` and `README.md`. Git gets `main` as the branch name, fast-forward-only merges and `pull.rebase false`. The `scripts` folder holds `pre-commit`, `validate-stack.sh` and `setup-hooks.sh`.

\`validate-stack.sh` calls three other skills: stack-validator, secrets-manager and docker-validation. Without them the check has nothing to run. The stack counts as done only when all three report no issues. When the direct route fails, the skill stops and asks you instead of improvising.

## Requirements
- Works with: GitLab, Docker

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-creator -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/stack-creator/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/stack-creator/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-creator -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/stack-creator/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-creator -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/stack-creator/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install rknall/claude-skills stack-creator
```

2. **Manually: put the files in place**
- File: `.github/skills/stack-creator/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-creator -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/rknall/claude-skills --path stack-creator
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/stack-creator/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-creator -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/rknall/claude-skills/tree/HEAD/stack-creator/SKILL.md

## When to use it
- lay out a new Docker stack with `config`, `secrets`, `_temporary` and `docs`
- set git to branch `main` with fast-forward-only merges
- generate a `.gitignore` that keeps `secrets/*` and `.env` out of commits
- add a `pre-commit` hook and `scripts/validate-stack.sh`
- start `docs/setup.md` and `docs/services.md` for a fresh stack

## Example prompts
- Create a new GitLab stack project with nginx and PostgreSQL for staging
- Initialize a Docker stack with `config`, `secrets` and `_temporary` folders and set up git on `main`
- Install the `pre-commit` hook for the new stack and run `scripts/validate-stack.sh`

## Similar
- [gitlab-cicd-pipeline](https://affpapa.org/en/nevibecode/skills/gitlab-cicd-pipeline.md) — skill · 673 installs
- [gitlab-ci-patterns](https://affpapa.org/en/nevibecode/skills/gitlab-ci-patterns.md) — skill · 13112 installs
- [cyrus-setup-gitlab](https://affpapa.org/en/nevibecode/skills/cyrus-setup-gitlab.md) — skill · 830 installs
- [Advanced GitLab MCP server](https://affpapa.org/en/nevibecode/mcp/advanced-gitlab-mcp-server.md) — MCP server · ★ 8 repo stars
- [ns-gitlab-board-sync](https://affpapa.org/en/nevibecode/skills/ns-gitlab-board-sync.md) — skill · 899 installs
- [stack](https://affpapa.org/en/nevibecode/skills/stack.md) — skill · 482 installs

From the same set: [rknall/claude-skills](https://affpapa.org/en/nevibecode/by/rknall/claude-skills.md) — 9 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
