dev-sanity

Name: dev-sanity
Availability: InStock
Author: buildooor

Validate local development environments with mode-driven health checks.

2|Updated Apr 4, 2026

Search Tags:#containers #health #local #dev #checks #repos

Ready to run

npx skills add https://github.com/build000r/skillbox --skill dev-sanity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-sanity
Source: https://github.com/build000r/skillbox/tree/main/skills/dev-sanity
Command: npx skills add https://github.com/build000r/skillbox --skill dev-sanity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Run mode-driven health checks to validate a local development environment.

Core Features & Use Cases

Mode-driven checks: Load repo, env, container, and health endpoint configurations from a private modes/config.sh file to surface misconfigurations before debugging.
Targeted validation: Verify repos exist, env files are present, containers are running, and health endpoints respond.
Use Case: Before starting a local stack, run dev-sanity to quickly surface the first failure and guide remediation.

Quick Start

Run the dev-sanity check against your configured local stack.

Frequently Asked Questions about dev-sanity

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

FAQPage Schema

How do I run health checks on my local dev environment before debugging?▼

Local dev environment health checks validate repo paths, verify environment files, check running Docker containers, and test HTTP health endpoints using a mode-driven configuration file. This surfaces the first startup failure quickly to guide remediation.

What does mode-driven validation mean for local development containers?▼

Mode-driven validation loads repo, environment, container, and health endpoint configurations from a private modes/config.sh file. It applies these configurations to check locally running Docker containers and surface any misconfigurations before you start debugging.

Do I need Docker and curl installed to validate my local development stack?▼

Yes, you need Docker and curl installed to validate your local development stack. Docker checks that local containers are running, while curl validates that HTTP health endpoints respond correctly during the environment validation process.

Can I check if my local Docker containers are running and env files exist before starting a stack?▼

Yes, you can verify that local Docker containers are running, repo paths exist, and environment files are present before starting a local stack. This targeted validation identifies configuration or startup issues early in development.

What is the best way to surface local dev configuration issues before debugging?▼

The best way to surface local dev configuration issues is to run a sanity check against your configured local stack. It validates repos, environment files, containers, and endpoints to pinpoint the first failure and guide remediation.