dev-script

Generate a single executable launcher for Docker Compose development stacks.

8|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/j0ruge/skills_commands_manager --skill dev-script
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-script
Source: https://github.com/j0ruge/skills_commands_manager/tree/main/plugins/dev-script/skills/dev-script
Command: npx skills add https://github.com/j0ruge/skills_commands_manager --skill dev-script

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Automates the bootstrapping of the entire local development stack by generating a single executable launcher.

Core Features & Use Cases

  • Generates a dedicated launcher script (dev.sh / dev.ps1) tailored to the detected project stack.
  • Performs per-service health checks, deterministic port reclaim, and a clean, idempotent re-run flow.
  • Optionally enables LAN TLS via mkcert + Caddy to support PKCE workflows across devices without editing source configs.

Quick Start

Run the provided dev.sh (or dev.ps1) to boot the entire local development stack with a single command.

Frequently Asked Questions about dev-script

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

FAQPage Schema
How do I automate bootstrapping a local development stack with Docker Compose?

Automate bootstrapping by generating a single executable launcher script that handles per-service health checks, deterministic port reclamation, and idempotent re-runs for your Docker Compose project.

What is the best way to run a multi-service Docker Compose project with a single command?

Running a multi-service stack is best handled by a generated launcher script that unifies the startup flow for frontend, backend, databases, and IdPs across platforms without modifying your source configuration.

Can I enable local TLS for Docker Compose development using mkcert and Caddy?

You can enable local TLS for Docker Compose development using mkcert and Caddy to support PKCE workflows across devices on your LAN without needing to edit your project's source configuration.

Does the generated launcher script support idempotent re-runs and cleanup?

The generated launcher script supports idempotent re-runs and cleanup, ensuring deterministic port reclamation and executing per-service health checks during every startup flow.

How do I handle port conflicts when starting my local Docker Compose stack?

Handle port conflicts when starting your Docker Compose stack by using a generated launcher script that performs deterministic port reclamation before booting the development environment.