GitLab Stack Validator — Claude Code skill: pre-deploy stack audit
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.
no license 297 installs ★ 93 updated 2025-10-20
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a claude-codeWhat GitLab Stack Validator 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.
What it helps with
- audit a stack layout before the first deploy
- catch credentials left in
.envor compose files - compare
.envwith.env.exampleand list mismatches - find root-owned files in the project tree
- confirm
.gitignorekeeps secrets out of the repo
Example prompts for the agent
- Validate this GitLab stack before I deploy it and give me a text report
- Check
.envagainst.env.exampleand list the variables that are missing - Audit
docker-compose.ymlfor secret handling and volume mounts
How to install GitLab Stack Validator
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a claude-code2Manually: put the files in place
~/.claude/skills/stack-validator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/stack-validator/
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a codex2Manually: put the files in place
.agents/skills/stack-validator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a cursor2Manually: put the files in place
.cursor/skills/stack-validator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rknall/claude-skills stack-validator2Manually: put the files in place
.github/skills/stack-validator/SKILL.md1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a gemini-cli2Platform CLI
gemini skills install https://github.com/rknall/claude-skills --path stack-validatorManually: put the files in place
.devin/skills/stack-validator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-validator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about GitLab Stack Validator
How do I install GitLab Stack Validator in Claude Code?
Run npx skills add rknall/claude-skills --skill stack-validator -a claude-code. The skill ends up at ~/.claude/skills/stack-validator/SKILL.md.
What does GitLab Stack Validator check?
Directory structure, file ownership, .gitignore entries, .env versus .env.example, and how Docker secrets are wired into docker-compose.yml.
Does it fix the issues it finds?
No. It reports them only; the changes are made by hand or through stack-creator and secrets-manager.