stack-validation

Validate Strut stack layouts, configurations, and prerequisites for deployment.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/gfargo/strut --skill stack-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-validation
Source: https://github.com/gfargo/strut/tree/main/.kiro/skills/stack-validation
Command: npx skills add https://github.com/gfargo/strut --skill stack-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stack Validation helps ensure Strut stacks are correctly configured, healthy, and auditable before deployment, reducing risk and drift.

Core Features & Use Cases

  • Runtime health checks to confirm services are running with healthy status
  • Drift detection and alignment vs. versioned stack configurations
  • Schema and environment validation to prevent deployment issues
  • Pre-deploy audits for new and existing stacks to catch issues early

Quick Start

To start, run the stack validation workflow for your target stack and review the diagnostic results before deployment.

Frequently Asked Questions about stack-validation

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

FAQPage Schema
How do I validate my Strut stack configuration before deployment?

You can validate your Strut stack configuration by running the stack validation workflow, which inspects docker-compose files, environment templates, and prerequisites to catch deployment issues early.

What is docker-compose stack drift detection and when do I need it?

Stack drift detection identifies misalignments between your running stack and versioned configurations. You need it during ongoing audits in staging or prod to maintain structural integrity and prevent configuration drift.

Can I run a health check on my docker-compose services to confirm they are running?

Yes, the stack validation process performs runtime health checks to confirm that your docker-compose services are running with a healthy status in both prod and staging environments.

Does stack validation work for both new stack creation and existing stack audits?

Yes, stack validation applies to both new stack creation and ongoing audits of existing stacks, applying deterministic rules to verify layouts, configuration files, and recommended best practices.

What's the best way to audit environment templates and prerequisites for a stack?

The best way to audit environment templates and prerequisites is to run a pre-deploy audit that inspects your docker-compose configurations and environment templates against deterministic validation rules and best-practice checks.

Why does my stack validation fail when checking backup and config verification?

Stack validation may fail if your docker-compose configurations, environment templates, or required prerequisites do not meet the deterministic deployment standards and recommended best-practice checks defined for your stack.