sql
Run SQL queries against the WordPress development database. Use when querying database tables, inspecting Simple History events, checking WordPress data, or debugging database issues.
When & Why to Use This Skill
This Claude skill empowers developers to interact directly with WordPress development databases by executing SQL queries through Docker Compose. It simplifies the process of inspecting table structures, monitoring Simple History events, and debugging data-related issues across various WordPress versions and environments, significantly accelerating the development and troubleshooting workflow.
Use Cases
- Debugging WordPress site activity: Querying the Simple History logs (wp_simple_history) to track recent administrative changes, plugin updates, or system errors.
- Data verification across environments: Checking record counts and data consistency across different WordPress installations, including nightly builds and version-specific setups (e.g., wp_6_6_ or wp_multisite_).
- Schema inspection: Quickly describing table structures (e.g., DESCRIBE wp_posts) to assist in writing custom queries or developing database-heavy plugins.
- Rapid database diagnostics: Running ad-hoc SQL commands like SHOW TABLES or COUNT(*) to perform health checks and maintenance without leaving the terminal or opening a GUI client.
| name | sql |
|---|---|
| description | Run SQL queries against the WordPress development database. Use when querying database tables, inspecting Simple History events, checking WordPress data, or debugging database issues. |
Run SQL Queries
You are tasked with running SQL queries against the WordPress development database.
Prerequisites
- Database credentials are stored in
CLAUDE.local.mdunder "Database Access" - Docker compose services must be running
- Commands must be run from the docker-compose project directory
Command Pattern
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "YOUR_SQL_HERE"
Refer to CLAUDE.local.md for the actual credentials and connection details.
Examples
Show all tables
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "SHOW TABLES;"
Query Simple History events
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "SELECT * FROM wp_simple_history ORDER BY id DESC LIMIT 10;"
Describe a table structure
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "DESCRIBE wp_simple_history;"
Count records
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "SELECT COUNT(*) FROM wp_posts;"
Table Prefixes
The database contains multiple WordPress installations with different prefixes:
| Prefix | Installation |
|---|---|
wp_ |
Main install (wordpress_mariadb) |
wp_nightly_ |
Nightly build |
wp_6_0_ to wp_6_6_ |
Version-specific installs |
wp_multisite_ |
Multisite install |
wp_php74_ |
PHP 7.4 install |
wp_subfolder_ |
Subfolder install |
Simple History Tables
The main Simple History tables (using wp_ prefix):
wp_simple_history- Main events tablewp_simple_history_contexts- Event context/metadata
Instructions
- Read credentials from
CLAUDE.local.md - Ask the user what SQL query they want to run (if not specified)
- Run the query using the command pattern above
- Display the results
- Offer to run follow-up queries if needed
Notes
- For complex queries, consider using
\Gat the end for vertical output - Be careful with UPDATE/DELETE queries - always confirm with user first