Agent skill

Docs

Update developer-facing documentation to reflect code changes on the current branch.

GPL-2.0Auto-check passed

Install Docs

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/docs .claude/skills/docs && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .claude/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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

$skill-installer install https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs

Type 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.

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/docs .agents/skills/docs && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .agents/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/docs .cursor/skills/docs && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .cursor/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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

$ gemini skills install https://github.com/wp-media/wp-rocket.git --path .claude/skills/docs

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/docs .gemini/skills/docs && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .gemini/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs

Installs 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).

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/docs .github/skills/docs && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .github/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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.

skills CLI

$ npx skills add wp-media/wp-rocket --skill docs -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install wp-media/wp-rocket docs --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/docs .opencode/skills/docs && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "docs" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/docs into .opencode/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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: docs
GitHub stars: 767
Token cost: ~1.1k tokens
SKILL.md length: 492 words
Files: 1
Skills in repo: 15
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: GPL-2.0

At a glance

Update developer-facing documentation to reflect code changes on the current branch.

Works in 5 steps: Read the changed files → Review existing documentation → Identify gaps → …
SKILL.md covers When to run / when to skip, Process and wp-rocket-specific notes
Calls git

What it does

Docs is an agent skill from wp-media/wp-rocket. Update developer-facing documentation to reflect code changes on the current branch. Runs as an inline skill inside backend-agent and frontend-agent (step 2.5 of the internal sequence) after implementation and before DOD. Receives the explicit list of changed files from the implementation agent. No-op if no public API changes occurred.

Its SKILL.md is about 1.1k 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: Performance optimization plugin for WordPress. The licence is GPL-2.0.

Example prompts

“/docs”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Read the changed files
Review existing documentation
Identify gaps
Update documentation
Return

What it can do on your machine

Read from SKILL.md and the folder at commit 3a96b66. 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
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

Docs loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 492 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

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

The full file from wp-media/wp-rocket at commit 3a96b66, republished under its GPL-2.0 licence (© wp-media). 492 words, ~1,082 tokens.

Download SKILL.mdSave it as .claude/skills/docs/SKILL.md (or your agent's skills folder).

name: docs
description: Update developer-facing documentation to reflect code changes on the current branch. Runs as an inline skill inside backend-agent and frontend-agent (step 2.5 of the internal sequence) after implementation and before DOD. Receives the explicit list of changed files from the implementation agent. No-op if no public API changes occurred.

DOCS SKILL

You are a technical writer updating internal developer documentation for WP Rocket. This skill runs inline inside the implementation agent and receives the list of changed files explicitly — do not infer scope from git.

When to run / when to skip

Run this skill if the implementation touched any of the following:

New or modified WordPress hooks (apply_filters, do_action, wpm_apply_filters_typed)
New or modified AJAX actions, REST routes, or WP-CLI commands
New or modified configuration keys, plugin options, or capabilities
New or modified BerlinDB tables, columns, or schemas
New or modified ServiceProvider bindings exposing a new public service
New or modified Subscriber get_subscribed_events() returns (new hooks subscribed)
New or modified plugin metadata (header constants, dependencies)
New or modified events / callbacks consumed by external integrations

Skip this skill (return no-op) if:

Implementation was internal refactoring only (private methods, no public surface change)
Only tests, build artifacts, or inc/Dependencies/ (vendored code) changed
Spec explicitly flags "no public API change"

When skipping, return:

json

{ "status": "SKIP", "reason": "No public API changes in this implementation" }

Process

Step 1 — Read the changed files

Use the Read tool on the explicit list provided by the implementation agent. Do not run git diff to discover scope — the agent already knows what changed.

Identify:

New or modified public API endpoints, hooks, AJAX actions, REST routes
Removed endpoints, hooks, or option keys (document as deprecated or removed)
New or modified capabilities (from the wordpress-compliance skill's list)

Step 2 — Review existing documentation

bash

find docs/ -name '*.md' -o -name '*.mdx' 2>/dev/null | head -50
ls -la README.md

Read relevant existing doc files. Understand what is already covered and what needs updating.

Step 3 — Identify gaps

For each significant public-facing change:

Is it documented? Is the existing doc current?
Which doc file should it go in? (existing or new)
For new hooks, follow the existing hook documentation convention (filter name, parameter types, return type, example).

Show full SKILL.md (204 more words)Show less

Step 4 — Update documentation

For each gap:

Find the correct existing file, or create a new one under docs/
Write or update the content
Stage the changes alongside the implementation commit (the implementation agent handles the actual git add / git commit).

Style guidelines:

Purpose: help engineers get a high-level understanding and find the relevant code fast
Tone: neutral, technical, not promotional
Structure: prose for explanations; bullets for parallel items; numbered steps for flows
Length: concise — a few hundred lines per file max; split by topic if large
Avoid embedding large code blocks; prefer referencing class/function names with their full namespace
Document the current state, not the change history (the changelog handles history)
For new filters, always include the wpm_apply_filters_typed() type as part of the signature

Step 5 — Return

json

{
  "status": "DONE|SKIP",
  "files_updated": ["docs/api/reports.md", "docs/configuration.md"],
  "files_created": ["docs/api/notifications.md"],
  "reason": "Populated if SKIP"
}

wp-rocket-specific notes

The docs root is docs/. The README at the repo root is for users; developer docs live in docs/.
For new filters, the docstring above wpm_apply_filters_typed() is the authoritative source. The doc file should reference (not duplicate) the docstring location: inc/Engine/Foo/Bar.php:42.
For new capabilities, add them to the list in .claude/skills/wordpress-compliance/SKILL.md (so PHPCS does not flag future uses).
For BerlinDB changes, document the migration version (YYYYMMDD format) and the upgrade path.

Files

Just SKILL.md in .claude/skills/docs of wp-media/wp-rocket.

Open the folder on GitHubat commit 3a96b66

Compare with similar skills

Docs 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.

Docs compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Docs this skillwp-media/wp-rocket	767	—	~1.1k	Automated safety check: Pass	GPL-2.0	today
WooCommerce Code Reviewwoocommerce/woocommerce	11k	3 repos	~1.1k	Automated safety check: Pass	Custom licence	today
Wp Block Developmentgambitph/Stackable	350	4 repos	~1.6k	Automated safety check: Pass	GPL-3.0	yesterday
Wp Interactivity APIAutomattic/agent-skills	211	3 repos	~1.5k	Automated safety check: Pass	None	8 mo ago
Postizgitroomhq/postiz-agent	506	2 repos	~7.9k	Automated safety check: Pass	AGPL-3.0	yesterday
Doc ScreenshotsWordPress/wordpress-playground	2k	—	~1.8k	Automated safety check: Pass	GPL-2.0	today

Similar skills

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.
11k GitHub starsUsed in 3 repos~1.1k tokens
DevelopmentAuto-check passed
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…
350 GitHub starsUsed in 4 repos~1.6k tokens
Auto-check passed
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…
211 GitHub starsUsed in 3 repos~1.5k tokens
DevelopmentAuto-check passed
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…
506 GitHub starsUsed in 2 repos~7.9k tokens
Writing & ContentAuto-check passed
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…
2k GitHub stars~1.8k tokensUpdated today
Testing & QAAuto-check passed
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
235 GitHub starsUsed in 1 repo~4.5k tokens
Business, Finance & HRAuto-check passed

Questions about Docs

What does Docs do?

Update developer-facing documentation to reflect code changes on the current branch. Docs is an agent skill from wp-media/wp-rocket. Update developer-facing documentation to reflect code changes on the current branch.

How do I install Docs in Claude Code?

Run `npx skills add wp-media/wp-rocket --skill docs -a claude-code`. Or copy the skill folder (.claude/skills/docs in wp-media/wp-rocket) into .claude/skills/docs in your project. Claude Code loads it when a task matches its description.

How do I install Docs in Codex?

Run `npx skills add wp-media/wp-rocket --skill docs -a codex`. Or copy the skill folder (.claude/skills/docs in wp-media/wp-rocket) into .agents/skills/docs in your project. Codex loads it when a task matches its description.

Can I use Docs 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 wp-media/wp-rocket --skill docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs, .gemini/skills/docs, .github/skills/docs and .opencode/skills/docs in your project.

What does Docs need to run?

Going by SKILL.md and its folder, Docs needs the command-line tools its instructions call (git).

Does Docs access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Docs 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 Docs use?

Docs is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Docs?

Skills that share tags, products or a category with Docs: WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Wp Block Development (gambitph/Stackable, 350 stars), Wp Interactivity API (Automattic/agent-skills, 211 stars) and Postiz (gitroomhq/postiz-agent, 506 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs?

wp-media (a GitHub organization) maintains it in wp-media/wp-rocket, which has 767 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: wp-media/wp-rocket on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Docs

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DOCS SKILL

When to run / when to skip

Process

Step 1 — Read the changed files

Step 2 — Review existing documentation

Step 3 — Identify gaps

Step 4 — Update documentation

Step 5 — Return

wp-rocket-specific notes

Files

Compare with similar skills

Similar skills

More from wp-media/wp-rocket

Related

Questions about Docs