WordPress-Simple-History

Adds changelog entries to readme.txt following keepachangelog format. Use when updating the Unreleased section or documenting changes for a release.

Reproducibly capture in-product UI screenshots (admin popovers, settings teasers, dashboard widgets) used as embedded images in premium upsell teasers. Use whenever a teaser image needs refreshing after the underlying UI changes.

Guides implementation of structured action links on log events. Use when adding get_action_links() to a logger or migrating from get_log_row_details_output().

Enforces active voice for logger messages and the Event Details API. Use when writing a new logger class or modifying message arrays in getInfo().

How to design and regenerate marketing screenshots for the wordpress.org plugin page (banner-1544x500.png, screenshot-1.png, etc). Covers the event mix that converts, the reproducible WordPress Playground pipeline that bakes it, and every non-obvious gotcha from previous shoots. Use when refreshing screenshot-1.png, banners, or any image showing the Simple History event log.

Guidance for writing and running tests in Simple History. Covers which framework to use, how to run existing tests, and how to create new ones (including the codegen recording workflow).

Surface and triage local issues that are safe and quick for an AI to implement and easy for a human to verify. Use when the user wants to "knock out issues", asks for "quick wins", "low-hanging fruit", "what's easy to do right now", or wants a batch of small tasks to work through in one session.

Use for quick local testing with WordPress Playground CLI. Spins up a disposable WordPress instance with the plugin mounted — no Docker needed. Ideal for worktrees, quick feature checks, and parallel testing on different branches.

Patterns for building WordPress admin page URLs in Simple History. Use when constructing admin links, settings tabs, or menu URLs dynamically.

Guides creation of custom loggers for Simple History. Use when building a new logger class to log WordPress events.

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.

Project-specific git commit guidance for Simple History. Use when committing changes, especially across core and premium plugins.

Manages the Simple History GitHub project board. Use when updating issue status, querying board items, or automating project workflows.

Formats markdown files using Prettier for consistent style. Use after creating or updating markdown files.

Patterns for passing data from PHP to React via wp_localize_script and REST API. Use when sharing config or data between PHP and React components.

Populates the event log with test data via WP-CLI. Use when adding sample events, generating test data, or benchmarking with realistic activity.

Translates Simple History Premium plugin strings for one or multiple locales. Use when translating or updating premium plugin PO files.

Updates the Simple History Premium plugin version in all required locations. Use when bumping or updating the premium version number.

Runs SQL queries against the WordPress development database. Use when inspecting tables, checking event data, or debugging database issues.

Reviews plugin code for WordPress.org compliance and trialware violations. Use when checking premium features, upsells, or license keys before submission.

Creates an isolated git worktree with its own WordPress test environment. Use when working on multi-day features or risky changes needing parallel testing.