validate-coolify-rules

Name: validate-coolify-rules
Availability: InStock
Author: chris78rey

Validate Docker configurations for Coolify production rule compliance.

Updated Feb 6, 2026

Search Tags:#devops #security #compliance #docker #infrastructure #validate #coolify

Ready to run

npx skills add https://github.com/chris78rey/en_construccion --skill validate-coolify-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-coolify-rules
Source: https://github.com/chris78rey/en_construccion/tree/main/.opencode/skills/validate-coolify-rules
Command: npx skills add https://github.com/chris78rey/en_construccion --skill validate-coolify-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams prevent production issues by validating code and configurations against Coolify's mandatory rules, catching prohibitions and compliance gaps before deployment.

Core Features & Use Cases

Rule-based validation to detect prohibited patterns such as exposed ports, host network_mode, hardcoded credentials, and unversioned images.
Actionable remediation guidance to fix violations and align with best practices.
Compliance reporting suitable for audits and change-control processes.

Quick Start

Run the validation against your repository's Docker-related assets to verify all Coolify rules are satisfied.

Frequently Asked Questions about validate-coolify-rules

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

FAQPage Schema

How do I validate docker-compose configurations for Coolify deployments?▼

Validate docker-compose configurations for Coolify by running this Skill to check for prohibited patterns. It enforces expose usage over ports, variable-based secrets, explicit healthchecks, non-root usage, and proper restart policies.

What are Coolify's mandatory production rules for Docker service definitions?▼

Coolify's mandatory production rules for Docker service definitions require using expose instead of ports, avoiding host network_mode, using variable-based secrets, pinning image versions, adding explicit healthchecks, and running as non-root.

How do I check my Docker-compose file for hardcoded credentials and exposed ports?▼

Check your Docker-compose file for hardcoded credentials and exposed ports by applying this Skill's rule-based validation, which detects prohibited patterns and provides actionable remediation guidance to fix violations.

Does this validation tool enforce healthchecks and restart policies in Coolify?▼

Yes, this validation tool enforces healthchecks and restart policies in Coolify. It applies breaking and positive rules to ensure your service definitions include explicit healthchecks and proper restart configurations before deployment.

Can I use this to generate compliance reports for Docker infrastructure audits?▼

Yes, you can use this to generate compliance reports for Docker infrastructure audits. The Skill produces compliance reporting suitable for audits and change-control processes by documenting intentional deviations from Coolify rules.

Why does my Coolify deployment fail with prohibited docker-compose patterns?▼

Your Coolify deployment may fail due to prohibited docker-compose patterns such as exposed ports, host network_mode, hardcoded credentials, or unversioned images. This Skill detects these violations and provides remediation guidance.