Verified:GitHub

GitLab Stack Validator

Validate GitLab stack projects for deployment readiness across eight configuration categories.

58|8|Updated Oct 18, 2025

Search Tags:#Docker #validation #environment #secrets #pre-deploy #stack #GitLab

One-click install

npx skills add https://github.com/rknall/claude-skills --skill gitlab-stack-validator

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: GitLab Stack Validator
Source: https://github.com/rknall/claude-skills/tree/main/stack-validator
Command: npx skills add https://github.com/rknall/claude-skills --skill gitlab-stack-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides thorough pre-deployment validation for GitLab stack projects, helping teams detect structure, environment, secrets, Docker, and ownership issues before they reach production, saving time and reducing deployment risk.

Core Features & Use Cases

Comprehensive Validation: 8 categories covering stack configuration and readiness checks
Environment Variable Synchronization: Ensures .env and .env.example are aligned for reliable deployments
Secrets Security: Verifies secrets are isolated in ./secrets and not exposed in git or env files
Docker Best Practices: Leverages docker-validation checks for container configurations
Detailed Reporting: Actionable findings with severity levels to guide remediation
Integration Ready: Works with companion skills like stack-creator and secrets-manager for fixes

Quick Start

In your stack project directory, run: claude "validate this stack" to generate a report, or provide a path to a stack directory to validate.

Frequently Asked Questions about GitLab Stack Validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate a GitLab stack project before deployment?▼

Stack validation checks your project's directory structure, environment variables, secrets management, Docker configuration, and file ownership to identify readiness issues. Run claude "validate this stack" in your stack directory to generate a structured findings report with severity levels for remediation.

What does pre-deployment stack validation check?▼

Pre-deployment validation covers eight categories: directory structure, environment variable synchronization between .env and .env.example, secrets isolation in ./secrets, Docker best practices, file ownership auditing, and git exposure risks. It detects configuration gaps without automatic fixes.

How do I ensure my environment variables are synchronized across .env files?▼

The validator compares .env and .env.example to detect misalignment, ensuring all required variables are documented and consistent. This prevents deployment failures caused by missing or undeclared environment settings.

Can I validate secrets are properly isolated and not exposed in GitLab?▼

Yes. The validator verifies secrets are confined to ./secrets and not leaked into git history, environment files, or Docker configurations. It reports exposure risks to guide security remediation before deployment.

Does stack validation work with Docker configurations?▼

Yes. The validator applies docker-validation checks to enforce container best practices within your stack project, ensuring Dockerfile and Docker Compose configurations meet deployment standards.

Can I use stack validation with other GitLab workflow tools?▼

Yes. The validator integrates with companion skills like stack-creator and secrets-manager, allowing you to validate before creation or after secret management updates, enabling coordinated remediation workflows.