WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
Reviews plugin code for WordPress.org compliance and trialware violations.
No licenceAuto-check passed
Install Wordpress Org Compliance
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-compliance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .claude/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .claude/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-complianceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-compliance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .agents/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .agents/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-compliance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .cursor/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .cursor/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bonny/WordPress-Simple-History.git --path .claude/skills/wordpress-org-compliance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-compliance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .gemini/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .gemini/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-complianceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .github/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .github/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bonny/WordPress-Simple-History wordpress-org-compliance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bonny/WordPress-Simple-History.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/wordpress-org-compliance .opencode/skills/wordpress-org-compliance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wordpress-org-compliance" agent skill from https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/wordpress-org-compliance into .opencode/skills/wordpress-org-compliance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wordpress-org-compliance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wordpress-org-compliance- GitHub stars
- 317
- Token cost
- ~540 tokens
- SKILL.md length
- 160 words
- Files
- 3
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Reviews plugin code for WordPress.org compliance and trialware violations.
- Checking premium features
- SKILL.md covers Core Rule: No Locked Code, Quick Reference, Key Patterns and Compliance Checklist, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- License keys before submission
What it does
Wordpress Org Compliance is an agent skill from bonny/WordPress-Simple-History. Reviews plugin code for WordPress.org compliance and trialware violations. Use when checking premium features, upsells, or license keys before submission.
Its SKILL.md is about 540 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `examples.md` and `testing.md`).
It works with WordPress. The repository describes itself as: 🔍🕵️♀️ WordPress audit log that track user changes in WordPress admin using a nice activity feed.
When your agent uses it
- Checking premium features
- License keys before submission
Example prompts
- “Use the wordpress-org-compliance skill to review plugin code for WordPress.org compliance and trialware violations”
- “/wordpress-org-compliance”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob
What it can do on your machine
Read from SKILL.md and the folder at commit 24f337f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are php).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developer.wordpress.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wordpress Org Compliance loads about 540 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 160 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 160 words (~540 tokens).
“Ensures WordPress.org compliance for free vs premium code and upselling.”
- name
- wordpress-org-compliance
- allowed-tools
- Read, Grep, Glob
- user-invocable
- false
Files
SKILL.md and 2 other files in .claude/skills/wordpress-org-compliance of bonny/WordPress-Simple-History.
- SKILL.md
- examples.md
- testing.md
Open the folder on GitHubat commit 24f337f
Compare with similar skills
Wordpress Org Compliance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wordpress Org Compliance this skillbonny/WordPress-Simple-History | 317 | — | ~540 | Automated safety check: Pass | None | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Wp Block Developmentgambitph/Stackable | 351 | 3 repos | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| Postizgitroomhq/postiz-agent | 508 | 2 repos | ~7.9k | Automated safety check: Pass | AGPL-3.0 | |
| Doc ScreenshotsWordPress/wordpress-playground | 2k | — | ~1.8k | Automated safety check: Pass | GPL-2.0 | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 235 | 1 repos | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Wp Block Development
gambitph/Stackable
A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…
Postiz
gitroomhq/postiz-agent
Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest…
Doc Screenshots
WordPress/wordpress-playground
Annotate UI screenshots with documentation callouts in Fellyph's established visual style — uniform-width orange arrows with white halos, double-stroke target outlines, numbered callout cards, dim…
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
Wp Interactivity API
Automattic/agent-skills
A skill your agent uses when building or debugging WordPress Interactivity API features (data-wp- directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration…
More from bonny/WordPress-Simple-History
All 21 skills in this repoBlueprint
bonny/WordPress-Simple-History
A skill your agent uses when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources…
Action Links
bonny/WordPress-Simple-History
Guides implementation of structured action links on log events.
Changelog
bonny/WordPress-Simple-History
Adds changelog entries to readme.txt following keepachangelog format.
Code Quality
bonny/WordPress-Simple-History
Runs linting and static analysis on PHP/CSS/JS using phpcs, phpstan, and rector.
Create Logger
bonny/WordPress-Simple-History
Guides creation of custom loggers for Simple History. An agent skill from bonny/WordPress-Simple-History.
Logger Messages
bonny/WordPress-Simple-History
Enforces active voice for logger messages and the Event Details API.
Related
Works with
Questions about Wordpress Org Compliance
What does Wordpress Org Compliance do?
Reviews plugin code for WordPress.org compliance and trialware violations. Wordpress Org Compliance is an agent skill from bonny/WordPress-Simple-History.org compliance and trialware violations.
When should I use Wordpress Org Compliance?
Wordpress Org Compliance fits situations like: checking premium features; license keys before submission.
How do I install Wordpress Org Compliance in Claude Code?
Run `npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a claude-code`. Or copy the skill folder (.claude/skills/wordpress-org-compliance in bonny/WordPress-Simple-History) into .claude/skills/wordpress-org-compliance in your project. Claude Code loads it when a task matches its description.
How do I install Wordpress Org Compliance in Codex?
Run `npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a codex`. Or copy the skill folder (.claude/skills/wordpress-org-compliance in bonny/WordPress-Simple-History) into .agents/skills/wordpress-org-compliance in your project. Codex loads it when a task matches its description.
Can I use Wordpress Org Compliance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bonny/WordPress-Simple-History --skill wordpress-org-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wordpress-org-compliance, .gemini/skills/wordpress-org-compliance, .github/skills/wordpress-org-compliance and .opencode/skills/wordpress-org-compliance in your project.
What does Wordpress Org Compliance need to run?
SKILL.md names no scripts, command-line tools or credentials: Wordpress Org Compliance is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.
Does Wordpress Org Compliance access the network?
SKILL.md names 1 domain. As links in the text: developer.wordpress.org. This is read from the text; nothing was executed.
Is Wordpress Org Compliance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wordpress Org Compliance use?
No licence was found for Wordpress Org Compliance or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Wordpress Org Compliance use?
About 540 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wordpress Org Compliance?
Skills that share tags, products or a category with Wordpress Org Compliance: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Wp Block Development (gambitph/Stackable, 351 stars), Postiz (gitroomhq/postiz-agent, 508 stars) and Doc Screenshots (WordPress/wordpress-playground, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wordpress Org Compliance?
bonny (a GitHub user) maintains it in bonny/WordPress-Simple-History, which has 317 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.
Source: bonny/WordPress-Simple-History on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.