Menu
Updates the Simple History Premium plugin version in all required locations. Use when bumping or updating the premium version number.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | premium-version-update |
| description | Updates the Simple History Premium plugin version in all required locations. Use when bumping or updating the premium version number. |
| argument-hint | <new-version> |
| allowed-tools | Read, Edit, Glob |
Update the Simple History Premium plugin version in all required locations.
See CLAUDE.local.md for the premium add-on path. Read it first to determine the correct path.
CLAUDE.local.md to find the premium add-on pathUpdate the version in these three locations (all relative to the premium add-on path):
Stable tag: lineVersion: line in the plugin header comment'version' value in the Config::init() arrayShow a summary of all changes made with before/after values.
/premium-version-update 1.10.0 — Update version to 1.10.0/premium-version-update 2.0.0 — Update version to 2.0.0Adds 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).