release
This skill uses Claude hooks which can execute code automatically in response to events. Review carefully before installing.
Release Process
Release checklist for Simple History core plugin and add-ons.
Uses OneFlow branching model and semver versioning.
Release Order
Always release core first, then premium/add-ons.
Premium declares a minimum core version. While reversing the order won't crash (premium shows a graceful admin notice), releasing core first ensures compatibility.
Core Plugin Release
1. Create Release Branch
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.
24wordpress-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().
13code-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.
10sql
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".
7github-project
Use when working with the Simple History GitHub project board — updating issue status, querying board items, or automating project workflows.
1