sql

bonny's avatarfrom bonny

Run SQL queries against the WordPress development database. Use when querying database tables, inspecting Simple History events, checking WordPress data, debugging database issues, or when the user says "run query" or "check database".

⭐313stars🔀74forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill enables developers to execute SQL queries directly against WordPress development databases within Docker environments. It streamlines database management by providing a bridge to MariaDB, allowing for real-time data inspection, debugging of database-level issues, and monitoring of Simple History events across multiple WordPress versions and installations.

Use Cases

  • Database Debugging: Quickly identify and resolve backend issues by querying WordPress tables and inspecting record states directly through the chat interface.
  • Activity Monitoring: Track system changes and user actions by retrieving and analyzing logs from Simple History tables (wp_simple_history).
  • Schema Inspection: Verify table structures, indexes, and prefixes across various WordPress environments, including multisite, nightly builds, and version-specific installs.
  • Data Validation & Reporting: Perform record counts and data integrity checks on core tables like wp_posts to ensure development environments are correctly populated and synchronized.
namesql
descriptionRun SQL queries against the WordPress development database. Use when querying database tables, inspecting Simple History events, checking WordPress data, debugging database issues, or when the user says "run query" or "check database".

Run SQL Queries

Run SQL queries against the WordPress development database.

Prerequisites

  • Database credentials are stored in CLAUDE.local.md under "Database Access"
  • Docker compose services must be running
  • Commands 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 table
  • wp_simple_history_contexts - Event context/metadata

Instructions

  1. Read credentials from CLAUDE.local.md
  2. Ask the user what SQL query they want to run (if not specified)
  3. Run the query using the command pattern above
  4. Display the results
  5. Offer to run follow-up queries if needed

Notes

  • For complex queries, consider using \G at the end for vertical output
  • Be careful with UPDATE/DELETE queries - always confirm with user first