Validate Laravel database configuration and test live connections.
npx skills add https://github.com/mim1012/ykp_project --skill db-validate
Please help me install this Agent Skill. Skill: db-validate Source: https://github.com/mim1012/ykp_project/tree/main/.claude/skills/db-validate Command: npx skills add https://github.com/mim1012/ykp_project --skill db-validate
This Skill quickly diagnoses and resolves common Laravel database connection issues, such as "connection refused," "access denied," or "database not found." It saves developers significant debugging time by pinpointing the exact cause of connectivity problems.
.env & config Validation: Checks database-related environment variables in .env and the config/database.php file for consistency and correctness..env, a missing database, or a misconfigured session driver, and provide the exact commands to fix it.My Laravel application is failing to connect to the database. Please use the db-validate skill to check the connection and suggest a fix.
High-intent search queries and answers about installing and using this skill.
Database connection errors in Laravel typically stem from incorrect .env credentials, misconfigured config/database.php, or a stopped database server. Validate your environment variables, verify driver, host, database name, username, and password match your actual database setup, then test the connection with a live connection attempt to pinpoint the exact failure point.
SQLSTATE[HY000] errors indicate a general database connection failure. Check that your PostgreSQL server is running and listening on the configured port, verify .env database credentials are correct, ensure the database exists, and confirm config/database.php maps environment variables properly before attempting a live connection test.
Yes, you can validate database configuration by checking .env values and config/database.php for consistency, verifying the database server is accessible on the correct host and port, and performing a live connection test via Laravel Tinker or DB::connection without deploying or running your full application.
Connection failures usually occur when PostgreSQL is not running, listens on a different port than configured, or credentials in .env are incorrect. Verify server status and port configuration, confirm .env values match your PostgreSQL setup, check that the database name exists, and test the live connection to identify the root cause.
Laravel database validation detects connection refused errors, access denied failures, missing databases, incorrect credentials, misconfigured drivers, empty host arrays, and mismatches between .env and config/database.php, reporting structured diagnostics with specific remediation steps for each error type.
No, you can test database connectivity changes immediately using a live connection test without restarting your application. This allows you to validate .env edits, credential updates, or PostgreSQL configuration changes instantly and confirm the connection works before deploying or running your full Laravel app.
gazollaConnect Java applications to Supabase PostgreSQL via JDBC with HikariCP pooling.
different-aiDiagnose Vercel production issues via live logs, deployments, and Neon Postgres.
HieubkavAutomate Laravel file and database backups with Spatie Laravel Backup.
SnakeODiagnose Laravel class, routing, and middleware errors with Artisan tooling.