stack-validator

Automate post-clone smoke testing for deployed Docker Compose stacks.

Updated May 21, 2026
One-click install
npx skills add https://github.com/furqan90/ai_mediated_platform_engineering --skill stack-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack-validator
Source: https://github.com/furqan90/ai_mediated_platform_engineering/tree/main/skills/stack-validator
Command: npx skills add https://github.com/furqan90/ai_mediated_platform_engineering --skill stack-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually verifying that a cloned deployment stack is fully functional after setup is tedious, inconsistent, and prone to human error, especially when working with multi-service Docker Compose environments that require sequential health checks and end-to-end route validation.

Core Features & Use Cases

  • Automated Stack Boot: Automatically starts the Docker Compose stack for the cloned project without manual intervention.
  • Health & Route Validation: Polls service health endpoints and hits public routes to confirm all components are functioning correctly.
  • Clear Test Summary: Prints an easy-to-read green/red summary of all smoke test results for quick status assessment.
  • Use Case: Platform engineers setting up a new project's on-prem deployment stack can use this skill to instantly verify the stack is ready for development immediately after cloning, eliminating hours of manual testing.

Quick Start

Use the stack-validator skill to run a full smoke test suite on the cloned orders-platform stack and receive a clear pass/fail summary of all validation checks.

Frequently Asked Questions about stack-validator

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

FAQPage Schema
How do I automate smoke testing for a Docker Compose stack after cloning?

You can automate smoke testing for a Docker Compose stack by orchestrating the service boot process, polling health endpoints, and validating public routes to generate a clear pass/fail summary.

What is the best way to validate the health of an on-prem deployment stack?

Validating an on-prem deployment stack is best done by automating post-clone health endpoint polling and public route validation, which replaces tedious manual verification workflows for multi-service environments.

Can I automatically verify public routes and service health for multi-service Docker environments?

Yes, you can verify public routes and service health for multi-service Docker environments by automatically polling endpoints and hitting routes to confirm all components function correctly after boot orchestration.

How do I get a clear pass/fail summary for deployment validation checks?

To get a clear pass/fail summary for deployment validation checks, run an automated end-to-end smoke test suite that prints an easy-to-read green and red status report of all validated services.

Does this stack validation approach work for multi-service environments requiring sequential health checks?

Yes, this stack validation approach works for multi-service environments by handling service boot orchestration and sequentially polling health endpoints to ensure all components are ready and functioning.

Why does manual verification of cloned deployment stacks fail?

Manual verification of cloned deployment stacks fails because it is tedious, inconsistent, and prone to human error, especially when sequential health checks and end-to-end route validation are required for multi-service environments.