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.
Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json.
Custom licenceAuto-check passed
Install Wp 71 Release Metadata
$ npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-release-metadata --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/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .claude/skills/wp-71-release-metadata && 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 "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .claude/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadataType 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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-release-metadata --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .agents/skills/wp-71-release-metadata && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .agents/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-release-metadata --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .cursor/skills/wp-71-release-metadata && 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 "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .cursor/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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/WordPress/Documentation-Issue-Tracker.git --path .github/skills/wp-71-release-metadata--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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-release-metadata --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .gemini/skills/wp-71-release-metadata && 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 "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .gemini/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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 WordPress/Documentation-Issue-Tracker wp-71-release-metadataInstalls 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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .github/skills/wp-71-release-metadata && 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 "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .github/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WordPress/Documentation-Issue-Tracker wp-71-release-metadata --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WordPress/Documentation-Issue-Tracker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/wp-71-release-metadata .opencode/skills/wp-71-release-metadata && 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 "wp-71-release-metadata" agent skill from https://github.com/WordPress/Documentation-Issue-Tracker/tree/main/.github/skills/wp-71-release-metadata into .opencode/skills/wp-71-release-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-71-release-metadata", 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
wp-71-release-metadata- GitHub stars
- 109
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,117 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json.
- Works in 12 steps: Every source file was included exactly… → Every source count or… → All ticket IDs are globally unique. → …
- Validate WordPress 7.1 release metadata from the local component files
- SKILL.md covers Files, Safety, Read component files and Create component entries, plus 4 more sections
- Reaches core.trac.wordpress.org
What it does
Wp 71 Release Metadata is an agent skill from WordPress/Documentation-Issue-Tracker. Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json. Use when asked to build, update, synchronize, reconcile, or validate WordPress 7.1 release metadata from the local component files.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with WordPress. The repository describes itself as: Issue Tracker for the WordPress Documentation team.
When your agent uses it
- Validate WordPress 7.1 release metadata from the local component files
Example prompts
- “/wp-71-release-metadata”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Every source file was included exactly once.
- Every source count or metadata.ticket_count equals its ticket array length.
- All ticket IDs are globally unique.
- The component ticket-count sum equals tickets_total_count_in_query.
- The three type counts sum to tickets_total_count_in_query.
- tickets_indexed_in_component_files equals tickets_reviewed.
- Pending tickets equal total minus reviewed and are not negative.
- No component has more reviewed tickets than tickets.
- Every component's issue candidates equal its dev-note, misc-dev-note, and field-guide counts; exclude is not an issue candidate.
- Global classification totals equal their component sums.
- Every component's created count equals its distinct referenced issues and does not exceed its candidate count.
- The global created count equals the number of distinct referenced issues across all tickets and does not exceed global candidates.
What it can do on your machine
Read from SKILL.md and the folder at commit 4377e0a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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 json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
core.trac.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
Wp 71 Release Metadata loads about 2.5k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,117 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,117 words (~2,467 tokens).
“Work only from repository files. Do not fetch Trac or GitHub data for this task.”
- name
- wp-71-release-metadata
Files
Just SKILL.md in .github/skills/wp-71-release-metadata of WordPress/Documentation-Issue-Tracker.
Open the folder on GitHubat commit 4377e0a
Compare with similar skills
Wp 71 Release Metadata 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 |
|---|---|---|---|---|---|---|
| Wp 71 Release Metadata this skillWordPress/Documentation-Issue-Tracker | 109 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| WooCommerce Code Reviewwoocommerce/woocommerce | 11k | 3 repos | ~1.1k | Automated safety check: Pass | Custom licence | |
| Wp Block Developmentgambitph/Stackable | 350 | 3 repos | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| Postizgitroomhq/postiz-agent | 505 | 2 repos | ~7.9k | Automated safety check: Pass | AGPL-3.0 | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 234 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Wp Interactivity APIAutomattic/agent-skills | 211 | 2 repos | ~1.5k | Automated safety check: Pass | None |
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…
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…
Wp Env
WordPress/agent-skills
A skill your agent uses when setting up, configuring, or troubleshooting local WordPress development environments with @wordpress/env (wp-env).
More from WordPress/Documentation-Issue-Tracker
Wp 71 Dev Note Issues
WordPress/Documentation-Issue-Tracker
Create missing WordPress 7.1 Dev Note and Field Guide tracking issues from 7-1-dev-notes/tickets.json in WordPress/Documentation-Issue-Tracker.
Related
Works with
Questions about Wp 71 Release Metadata
What does Wp 71 Release Metadata do?
Populate or refresh 7-1-dev-notes/release-metadata.json from every JSON file in 7-1-dev-notes/components/ and validate it against release-metadata.schema.json. Wp 71 Release Metadata is an agent skill from WordPress/Documentation-Issue-Tracker.json.
When should I use Wp 71 Release Metadata?
Wp 71 Release Metadata fits situations like: validate WordPress 7.1 release metadata from the local component files.
How do I install Wp 71 Release Metadata in Claude Code?
Run `npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a claude-code`. Or copy the skill folder (.github/skills/wp-71-release-metadata in WordPress/Documentation-Issue-Tracker) into .claude/skills/wp-71-release-metadata in your project. Claude Code loads it when a task matches its description.
How do I install Wp 71 Release Metadata in Codex?
Run `npx skills add WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a codex`. Or copy the skill folder (.github/skills/wp-71-release-metadata in WordPress/Documentation-Issue-Tracker) into .agents/skills/wp-71-release-metadata in your project. Codex loads it when a task matches its description.
Can I use Wp 71 Release Metadata 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 WordPress/Documentation-Issue-Tracker --skill wp-71-release-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-71-release-metadata, .gemini/skills/wp-71-release-metadata, .github/skills/wp-71-release-metadata and .opencode/skills/wp-71-release-metadata in your project.
What does Wp 71 Release Metadata need to run?
SKILL.md names no scripts, command-line tools or credentials: Wp 71 Release Metadata is instructions for the agent only.
Does Wp 71 Release Metadata access the network?
SKILL.md names 1 domain. In commands or code: core.trac.wordpress.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Wp 71 Release Metadata 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 Wp 71 Release Metadata use?
Wp 71 Release Metadata has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Wp 71 Release Metadata use?
About 2.5k tokens (SKILL.md is roughly 9.9k 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 Wp 71 Release Metadata?
Skills that share tags, products or a category with Wp 71 Release Metadata: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Wp Block Development (gambitph/Stackable, 350 stars), Postiz (gitroomhq/postiz-agent, 505 stars) and Wp Performance Review (elvismdev/claude-wordpress-skills, 234 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wp 71 Release Metadata?
WordPress (a GitHub organization) maintains it in WordPress/Documentation-Issue-Tracker, which has 109 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 22, 2026.
Source: WordPress/Documentation-Issue-Tracker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.