troubleshoot-local-dev

Diagnose and fix Docker-based local development environment startup issues.

1|1|Updated Dec 16, 2023
One-click install
npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill troubleshoot-local-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-local-dev
Source: https://github.com/sjtw/tarkov-build-optimiser/tree/main/.cursor/skills/troubleshoot-local-dev
Command: npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill troubleshoot-local-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix common local development environment issues.

Core Features & Use Cases

  • Provides structured diagnostic steps for starting services, checking logs, and verifying configurations.
  • Covers common failure scenarios (services not starting, unhealthy containers, missing environment variables, failed migrations) and offers concrete remediation paths.
  • Useful for developers and DevOps engineers maintaining Docker-based local stacks.

Quick Start

Start by running the guided diagnostic routine to identify and fix startup problems in the local dev environment.

Frequently Asked Questions about troubleshoot-local-dev

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

FAQPage Schema
How do I troubleshoot Docker containers failing to start in my local dev environment?

To troubleshoot local dev startup issues, run structured diagnostic checks to validate environment variables, inspect noisy logs, and apply concrete remediation steps to restore unhealthy containers.

Why are my Postgres database migrations failing when I bring up my Docker stack?

Failed migrations often stem from missing environment variables or unhealthy container states; validate your Postgres configuration and apply structured diagnostic checks to identify and fix the startup blocker.

What is the best way to diagnose missing environment variables in a Docker development setup?

Diagnosing missing environment variables requires running validation checks against your Docker configuration to catch errors preventing containers from running and provide concrete remediation paths.

How do I fix unhealthy Docker containers preventing my local services from starting?

Fix unhealthy containers by following guided diagnostic routines that inspect service logs, verify configurations, and execute remediation steps to restore a healthy local workflow.

Can I use this diagnostic routine for non-Docker local development stacks?

This diagnostic routine specifically targets Docker-based development stacks, providing structured checks for container services, environment variables, and Postgres migrations to restore local workflow.

What should I do when my local dev services won't start and the logs are too noisy to read?

When noisy logs obscure local dev startup failures, apply structured diagnostic steps to filter log noise, validate environment variables, and resolve configuration errors preventing services from running.