env-health

Diagnose and fix Laravel environment configuration issues using Artisan and CLI tools.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mim1012/ykp_project --skill env-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: env-health
Source: https://github.com/mim1012/ykp_project/tree/main/.claude/skills/env-health
Command: npx skills add https://github.com/mim1012/ykp_project --skill env-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common headaches of debugging Laravel environment configuration, cache, and database connection problems. It prevents wasted time on "why isn't my config working?" scenarios by providing immediate diagnostics and solutions.

Core Features & Use Cases

  • Comprehensive Environment Check: Verifies critical settings like APP_ENV, DB_CONNECTION, SESSION_DRIVER, and CACHE_STORE against expected values for your development environment.
  • .env File Validation: Ensures your .env file is correctly configured and not being overridden by stale cached configurations.
  • Live Database Connection Test: Performs a real-time database connection test, reporting success or detailed error messages to pinpoint connectivity issues.
  • Use Case: When you encounter a "Database connection error" or "SQLite connection attempt" after a deployment or local setup, this Skill automatically runs a full diagnostic, identifies the root cause (e.g., wrong DB_CONNECTION in .env or stale cache), and suggests the exact fix.

Quick Start

My Laravel app is showing a "Database connection error". Please run the env-health skill to diagnose and fix the problem.

Frequently Asked Questions about env-health

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

FAQPage Schema
How do I fix Laravel database connection errors after configuration changes?

Laravel database connection errors often stem from stale cache or mismatched .env settings. env-health diagnoses your environment by validating .env values, testing live database connectivity, and identifying root causes like wrong DB_CONNECTION or cached config, then provides exact remediation steps.

Why isn't my Laravel .env file taking effect after I updated it?

.env modifications are frequently ignored due to cached configuration in Laravel. env-health checks if your .env file is correctly configured and detects stale cache overrides, then guides you through clearing caches to restore the changes.

Can I diagnose SQLite connection problems in my Laravel development environment?

Yes. env-health runs real-time database connection tests and reports detailed error messages specific to SQLite or other DB_CONNECTION types, pinpointing whether the issue is configuration, file permissions, or connectivity.

How do I verify my Laravel environment variables are set correctly?

env-health performs comprehensive environment checks against critical settings like APP_ENV, DB_CONNECTION, SESSION_DRIVER, and CACHE_STORE, verifying each matches expected values for your development or staging scenario.

What should I do when Laravel configuration isn't reflecting after deployment to staging?

Configuration changes often fail to propagate due to cache or incorrect .env setup. env-health automates full diagnostics of environment state and database connectivity, identifies the root cause, and suggests restart guidance and exact fixes.