# GitLab Stack Validator

GitLab Stack Validator audits a GitLab stack project before deployment: directory layout, secrets, .env sync and Docker config. Reports problems; fixing them is on you.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 297 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-validator/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-validator

## What it does

Runs a pre-deploy audit of a GitLab stack project. The layout comes first: `./config`, `./secrets` and `./_temporary` have to be there, access to `./secrets` should be locked down, and nothing in the tree should belong to root. It also reads `.gitignore` to confirm that secrets, temp files and `.env` stay out of git.

Then `.env` gets compared with `.env.example`. A missing template file or a variable present on one side only goes into the report. Docker config is handed to the `docker-validation` skill: secrets declared at the top level, services pulling them through the `secrets:` key, volumes pointing at the right folders, no `version:` field in `docker-compose.yml`. Credentials written straight into a compose file, `.env` or a shell script are marked critical.

Detection and reporting are all this skill does. Remediation sits with `stack-creator` and `secrets-manager`, so on a project without them you apply the fixes yourself. Custom rules live in `.stack-validator.yml`, and the report comes out as text or JSON.

## Requirements
- Works with: GitLab, Docker

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add rknall/claude-skills --skill gitlab-stack-validator -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-validator/SKILL.md

## When to use it
- audit a stack layout before the first deploy
- catch credentials left in `.env` or compose files
- compare `.env` with `.env.example` and list mismatches
- find root-owned files in the project tree
- confirm `.gitignore` keeps secrets out of the repo

## Example prompts
- Validate this GitLab stack before I deploy it and give me a text report
- Check `.env` against `.env.example` and list the variables that are missing
- Audit `docker-compose.yml` for secret handling and volume mounts

## Similar
- [gitlab-ci-patterns](https://affpapa.org/en/nevibecode/skills/gitlab-ci-patterns.md) — skill · 13112 installs
- [gitlab-cicd-pipeline](https://affpapa.org/en/nevibecode/skills/gitlab-cicd-pipeline.md) — skill · 673 installs
- [gitlab-ci-validator](https://affpapa.org/en/nevibecode/skills/gitlab-ci-validator.md) — skill · 758 installs
- [gitlab-workflow](https://affpapa.org/en/nevibecode/skills/gitlab-workflow.md) — skill · 1100 installs
- [building-gitlab-ci-components](https://affpapa.org/en/nevibecode/skills/building-gitlab-ci-components.md) — skill · 1 install
- [gitlab-automation](https://affpapa.org/en/nevibecode/skills/gitlab-automation.md) — skill · ★ 3785 repo stars

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
