Agent skill · software engineering · rknall
GitLab Stack Config Generator
Generates service-specific configuration files for GitLab stack projects in ./config directory, using .env as the primary configuration source. Creates nginx, PostgreSQL, Redis, and custom service configs with strict validation for secrets, paths, and Docker best practices. Use when setting up service configurations, creating config templates, or ensuring configs follow stack patterns.
Why this skill is useful
Adds executable scripts for generating and validating service-specific configuration files that follow strict Docker and environment variable best practices.
What it needs
Requires docker installed locally. About 9k tokens when loaded. Last updated 2025-10-20. 58 stars on the source repository.
What this skill does
GitLab Stack Config Generator This skill generates and manages service-specific configuration files for GitLab stack projects, ensuring configurations follow proper patterns, use .env for all variables, and never contain secrets. When to Use This Skill Activate this skill when the user requests: Generate configuration files for services (nginx, PostgreSQL, Redis, etc.) Create config templates for new services Set up ./config directory structure Validate existing configuration files Ensure configs use .env variables correctly Check that configs don't contain secrets Set up project meta files (CLAUDE.md, .gitignore, .dockerignore) Sync .env and .env.example Core Configuration Principles CRITICAL RULES: 1. ./env is Configuration Source: All configuration variables in .env (NOT in config files) 2. No Secrets in Configs: NEVER put secrets in configuration files (use secrets-manager) 3. Service Directories: Each service gets ./config/service-name/ directory 4. Flat Inside Service: Config files flat inside service directory 5. .env Sync: .env and .env.example MUST always match 6. Path Validation: All referenced paths must exist 7. Docker Validation: Use docker-validation skill for Docker configs 8. Project Meta Files: CLAUDE.md, .gitignore, .dockerignore required Configuration Workflow Phase 1: Understanding Requirements Step 1: Determine What to Generate Ask the user (or infer): Which services need configuration? New configs or updating existing? Production, development, or both? Which templates to use (if any)? Step 2: Check Current State 1. Does ./config directory exist? 2. Does .env exist? 3. Does .env.example exist? 4. Do service directories already exist? 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rknall/config-generator