wordpress-org-compliance
WordPress.org Plugin Compliance
Ensures WordPress.org compliance for free vs premium code and upselling.
Core Rule: No Locked Code
Golden Rule: All code in WordPress.org plugins must be free and fully functional.
- Every feature works completely without a license key
- No trial periods or usage limits
- No features requiring payment to unlock
Quick Reference
Not Allowed
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.
24logger-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.
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