wp-media

User-facing entry point for the wp-rocket issue workflow. Invoke directly to start a delivery run from a GitHub issue number, URL, or raw description. Runs inline in your conversation context; spawns specialist agents (ticket-writer, grooming-agent,…

Use this skill when adding or modifying WordPress abilities

Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.

Check a change against WordPress.org plugin rules and PHPCS standards.

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…

Run the Definition of Done checklist for the current wp-rocket branch and report PASS/WARN/FAIL with evidence. Two modes: layer 1 (self-correction inside backend-agent / frontend-agent — resolves FAILs before handoff) and layer 2 (independent orchestrator…

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.

User-facing entry point for the agentic delivery pipeline. Invoke directly — or via "work on issue 123" / "/task 123" / "#123" / a pasted description — to start a delivery run. Runs inline in your conversation context; spawns specialist agents (ticket-writer,…

Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.

Generate a categorized changelog from merged PRs since the last release. Use when asked for "changelog", "release notes", or "what changed since last release".

Update developer-facing documentation to reflect code changes. Runs two ways: (1) inline inside the implementer (step 2.5) where it receives the explicit list of changed files, and (2) standalone when a user invokes it directly, where it discovers scope…

Run the Definition of Done checklist for the current branch and report PASS/WARN/FAIL with evidence. Works in the delivery pipeline (layer 1 self-check inside the implementer; layer 2 independent gate from the orchestrator) and as a standalone skill a user…

Consult group.one coding and technical recommendations (GOPEN) when setting up a new repository, scaffolding new components, choosing an architecture pattern, or when the user asks to improve structure/quality according to group.one guidelines. Do NOT invoke…

Groom a single issue — produce an implementation spec and optionally post the grooming summary as an issue comment. Standalone entry point for the grooming-agent.

Read and refresh a pre-built dependency graph at .claude/graph/dependency-graph.json. Use to locate where a symbol is defined, trace dependencies, find where a service is wired, or enumerate the handlers/registrations in a module — without re-scanning the…

Generate a bespoke issue-workflow for any target project. Phase 1 — a Claude Opus analyst reads the project deeply and produces a disposition report. Phase 2 — on approval, parallel writer agents transplant every Maestro workflow component, adapted to the…

Show the Maestro command map — a quick reference to all available skills.

Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.

Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment. Standalone entry point for the qa-engineer agent.

Run a lead code review on the current branch or a given PR. Standalone entry point for the lead-reviewer agent.

Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.

Check a change against WordPress.org plugin rules and PHPCS standards.

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

Orchestrated audit of the current repo's open GitHub-issue backlog — fans out code-review and per-issue categorization agents, verifies which issues are already fixed, and produces a ranked shortlist of AI-autonomous quality wins plus a full triage (Should…

Show the Cadenza command map — a quick reference to all available agents and commands.

Produce a per-person Sentry activity dashboard (archives, resolves, notes with a heatmap) across projects for a given period. Requires the Sentry MCP.

Triage new, regressed, and escalating Sentry production errors — score them, post triage notes, and draft GitHub issues for the important ones (requires the Sentry MCP).

Write a paste-ready Slack sprint message (kick-off / mid-sprint / end-of-sprint) from a GitHub Projects sprint.

Turn raw context, a thread, or a rough note into a well-structured GitHub issue.

Generate a PO-ready grouped changelog from merged PRs since the last release.

Generate a PR description for the current branch using commits, diffs, and the project template.

Run E2E smoke tests (basic) or full acceptance + regression suite (extended).

Build, inspect, and manage versions of the WP-Media WordPress plugins registered in apvm (BackWPup — `free`, `pro-de`, `pro-en` variants — WP Rocket, and Imagify) with the apvm CLI (Automation Plugin Version Manager). Covers `apvm build` (from a PR, branch,…