sql
Run SQL Queries
Run 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 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
More from bonny/wordpress-simple-history
changelog
Adds changelog entries to readme.txt following keepachangelog format. Use when updating the Unreleased section or documenting changes for a release.
23wordpress-org-compliance
Reviews plugin code for WordPress.org compliance and trialware violations. Use when checking premium features, upsells, or license keys before submission.
17logger-messages
Enforces active voice (verb-first) for all Simple History logger messages and the Event Details API for details output. Triggers: creating a new logger class, writing or modifying a 'messages' array in get_info()/getInfo(), calling notice_message/warning_message/info_message, or implementing get_log_row_details_output().
13release
Release checklist for core and premium plugins. Covers version bumping, changelog finalization, tagging, and deployment. Triggers when user says "release", "publish", "deploy", "bump version", "prepare release".
10code-quality
Runs linting and static analysis on PHP/CSS/JS using phpcs, phpstan, and rector. Use when checking code style, fixing lint errors, or running static analysis.
10github-project
Use when working with the Simple History GitHub project board — updating issue status, querying board items, or automating project workflows.
1