| name | database-verification |
| description | Shell-based database connectivity and integrity checks. Verifies that databases are reachable, schemas match expectations, and data integrity constraints hold.
|
| requires | {"bins":[]} |
Database verification skill using standard database CLI tools.
When to activate
Use this skill when tests fail with connection errors or timeouts to a
database, when database-related tests exist in the test suite, when
docker-compose or similar configs define database services, or when a
migration has recently been applied and needs verification.
Connectivity checks
Test reachability before running any data queries. Each database has its
own tool:
PostgreSQL
pg_isready -h host -p 5432
Returns exit code 0 if accepting connections. For authenticated check:
psql -h host -p 5432 -U user -d dbname -c "SELECT 1"
Redis
redis-cli -h host -p 6379 ping
Expected response: PONG.
SQLite
sqlite3 /path/to/file.db ".tables"
Returns the list of tables. A missing file or corrupt database produces
an error.
MySQL / MariaDB
mysql -h host -u user -p -e "SELECT 1"
Or check just connectivity:
mysqladmin -h host -u user ping
MongoDB
mongosh --host host --port 27017 --eval "db.runCommand({ ping: 1 })"
Schema verification
After connectivity is confirmed:
