database-verification

Database verification scripts check connectivity and schema integrity by running read-only validations to ensure services are reachable and expected tables or constraints exist. This skill generates a standardized health report confirming migration status across PostgreSQL, Redis, SQLite, MySQL, and MongoDB.

The best way to verify data consistency across multiple systems is using standardized health checks that validate schemas and constraints. This skill identifies connectivity issues and checks data integrity across PostgreSQL, MySQL/MariaDB, MongoDB, Redis, and SQLite.

Yes, you can perform read-only database health checks for containerized services. This skill verifies Docker health status and checks database connectivity when containerized services start, ensuring databases are reachable without modifying data.

Yes, database verification works with PostgreSQL, MongoDB, and Redis, alongside SQLite and MySQL/MariaDB. The skill identifies and verifies connectivity, schema integrity, and data consistency across all supported database systems.

Yes, you need specific CLI tools installed to verify database schema and connectivity. The skill automatically checks for required command-line tools before executing read-only validations against your database environment.

Database health checks report connection errors after applying migrations when services are unreachable or schemas mismatch expectations. This skill identifies connectivity issues, verifies migration status, and reports findings in a standardized health report.