Release Blog Drafter
obot-platform/obot
Drafts a release announcement blog post for an obot release as a Markdown file, with an optional WordPress draft through MCP and no live publishing without confirmation.
Work on a GitHub issue by number for wp-media/wp-rocket. An agent skill from wp-media/wp-rocket.
GPL-2.0Auto-check passed
Install Issue Workflow
$ npx skills add wp-media/wp-rocket --skill issue-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wp-media/wp-rocket issue-workflow --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/wp-media/wp-rocket.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/issue-workflow .claude/skills/issue-workflow && 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 "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .claude/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflowType 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 wp-media/wp-rocket --skill issue-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wp-media/wp-rocket issue-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/issue-workflow .agents/skills/issue-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .agents/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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 wp-media/wp-rocket --skill issue-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wp-media/wp-rocket issue-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/issue-workflow .cursor/skills/issue-workflow && 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 "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .cursor/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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/wp-media/wp-rocket.git --path .claude/skills/issue-workflow--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 wp-media/wp-rocket --skill issue-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wp-media/wp-rocket issue-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/issue-workflow .gemini/skills/issue-workflow && 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 "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .gemini/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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 wp-media/wp-rocket issue-workflowInstalls 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 wp-media/wp-rocket --skill issue-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/issue-workflow .github/skills/issue-workflow && 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 "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .github/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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 wp-media/wp-rocket --skill issue-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wp-media/wp-rocket issue-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wp-media/wp-rocket.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/issue-workflow .opencode/skills/issue-workflow && 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 "issue-workflow" agent skill from https://github.com/wp-media/wp-rocket/tree/develop/.claude/skills/issue-workflow into .opencode/skills/issue-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-workflow", 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
issue-workflow- GitHub stars
- 767
- Used in
- 1 other repo
- Token cost
- ~756 tokens
- SKILL.md length
- 337 words
- Files
- 6 (incl. scripts)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- GPL-2.0
At a glance
Work on a GitHub issue by number for wp-media/wp-rocket. An agent skill from wp-media/wp-rocket.
- Works in 6 steps: Extract the issue number from the user's… → Fetch the issue — run bash… → Check for parent epics — if Parent Epic… → …
- SKILL.md covers Tooling and Steps
- Runs Shell and JavaScript scripts from its folder; calls bash, git and gh
What it does
Issue Workflow is an agent skill from wp-media/wp-rocket. Work on a GitHub issue by number for wp-media/wp-rocket. Fetches the issue and hands control to the orchestrator skill (running inline in this conversation), which manages grooming, spec review, implementation, lead review, CI, and QA end-to-end.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `refs/pr-template.md`, `scripts/init-pr-draft.sh` and `scripts/issue-sync.sh`).
It works with GitHub, WordPress, Model Context Protocol and Bash. The repository describes itself as: Performance optimization plugin for WordPress. The licence is GPL-2.0.
Example prompts
- “/issue-workflow”
Requirements
- Node.js
- A Bash shell
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Extract the issue number from the user's message.
- Fetch the issue — run bash .claude/skills/issue-workflow/scripts/issue-sync.sh (or use the MCP equivalent). Read the resulting file at…
- Check for parent epics — if Parent Epic (GitHub) or Parent Epics (Task List) has entries, sync each parent with issue-sync.sh and read…
- Check if this is an Epic — if the issue has label epics, Issue Type EPIC, or has sub-issues listed, ask the user: "Work the epic as a…
- Determine base branch — default is origin/develop unless the user specified otherwise.
- Invoke the orchestrator skill inline (do not spawn it as a sub-agent — it runs in this conversation context so it can read the user's…
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
Ships 4 files in scripts/ (Shell and JavaScript), which the agent can run.
Shell commands in SKILL.md call:
bashgitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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
Issue Workflow loads about 756 tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 337 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); the scripts in this folder 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). 337 words, ~756 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-workflow/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- issue-workflow
- description
- Work on a GitHub issue by number for wp-media/wp-rocket. Fetches the issue and hands control to the orchestrator skill (running inline in this conversation), which manages grooming, spec review, implementation, lead review, CI, and QA end-to-end.
Issue Workflow
Repository: wp-media/wp-rocket
When the user asks to work on an issue by number, such as:
/task 123issue 123#123
follow this workflow. The orchestrator runs inline in this conversation — read the user's opening message before kicking it off, since it uses that for escalation calibration (high autonomy / standard / high oversight).
Tooling
Use shell commands as the primary approach. The GitHub MCP (mcp_github_*) may be used if it is connected — but shell is always the safe fallback and is preferred for reliability.
| Operation | Shell (primary) | GitHub MCP (if connected) |
|---|---|---|
| Issue fetch | bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N> | mcp_github_github_issue_read |
| Branch creation | bash .claude/skills/issue-workflow/scripts/make-issue-branch.sh | — |
| Staging & committing | git add / git commit | — |
| Pushing | git push -u origin <branch> | — |
| PR creation | gh pr create | mcp_github_github_create_pull_request |
| CI monitoring | gh pr checks <PR#> | mcp_github_github_pull_request_read |
Steps
Extract the issue number from the user's message.
Fetch the issue — run
bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>(or use the MCP equivalent). Read the resulting file at.TemporaryItems/Issues/wp-rocket/issues/<N>.md.Check for parent epics — if
Parent Epic (GitHub)orParent Epics (Task List)has entries, sync each parent withissue-sync.sh <epic-N>and read those files for context.Check if this is an Epic — if the issue has label
epics, Issue TypeEPIC, or has sub-issues listed, ask the user: "Work the epic as a whole, or a specific sub-issue?" If a sub-issue is chosen, sync it and proceed with the epic context in mind.Determine base branch — default is
origin/developunless the user specified otherwise.Invoke the
orchestratorskill inline (do not spawn it as a sub-agent — it runs in this conversation context so it can read the user's intent for escalation calibration):Inputs: issue number
N, issue file.TemporaryItems/Issues/wp-rocket/issues/<N>.md, base branch
The orchestrator skill manages everything from here: calibration → grooming → spec review → dispatch → implementation → lead review → push & PR → CI → QA → finalize. It spawns the specialist agents (grooming-agent, challenger, backend-agent, frontend-agent, release-agent, lead-reviewer, qa-engineer, ticket-writer) as isolated sub-agents, but the orchestrator itself stays inline so it can surface decisions back to the user naturally.
Monitor progress at .TemporaryItems/Issues/wp-rocket/issue-<N>-workflow-log.html.
© wp-media, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts) in .claude/skills/issue-workflow of wp-media/wp-rocket.
- SKILL.md
- refs/pr-template.md
- scripts/init-pr-draft.sh
- scripts/issue-sync.sh
- scripts/make-issue-branch.sh
- scripts/slack-notify.js
Open the folder on GitHubat commit 3a96b66
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wp-media/wp-rocket, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Issue Workflow 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 |
|---|---|---|---|---|---|---|
| Issue Workflow this skillwp-media/wp-rocket | 767 | 1 repos | ~756 | Automated safety check: Pass | GPL-2.0 | |
| Release Blog Drafterobot-platform/obot | 1.1k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Releasejgravelle/jcodemunch-mcp | 2.7k | — | ~6.5k | Automated safety check: Pass | Custom licence | |
| Keeljoseconti/declaracion-renta-espana | 190 | — | ~11k | Automated safety check: Warn | GPL-3.0-or-later | |
| Action Runnermajiayu000/claude-skill-registry | 666 | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Clientmajiayu000/claude-skill-registry | 666 | 1 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Release
jgravelle/jcodemunch-mcp
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.
Keel
joseconti/declaracion-renta-espana
A skill your agent uses for ANY new software project from idea to release — websites, WordPress/WooCommerce plugins, MCP servers, web apps, components, or libraries.
Action Runner
majiayu000/claude-skill-registry
Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the…
MCP Client
majiayu000/claude-skill-registry
Universal MCP client for connecting to any MCP server with progressive disclosure.
Env Setup
majiayu000/claude-skill-registry
Claude Code 环境一键同步工具。从 GitHub 仓库同步所有配置到本地：output-styles 风格、CLAUDE.md 全局提示词、MCP 服务器配置、Agent 配置、Plugin 配置。适用于多设备统一环境、换电脑恢复、团队共享配置等场景。当用户需要从 GitHub 仓库同步 Claude Code/OpenClaw 环境配置时使用此 skill。
More from wp-media/wp-rocket
All 15 skills in this repoKnowledge Graph
wp-media/wp-rocket
Read and refresh wp-rocket's pre-built dependency graph at .claude/graph/dependency-graph.json.
Wordpress Compliance
wp-media/wp-rocket
A skill your agent uses when modifying templates, admin UI, output, hooks, plugin metadata, sanitization, escaping, or any code that must remain compliant with WordPress.org and repository PHPCS…
Wp Rocket Architecture
wp-media/wp-rocket
A skill your agent uses when changing service structure, Subscribers, ServiceProviders, Container wiring, bootstrapping, Context classes, or any code that may affect the core caching engine in WP…
Challenge
wp-media/wp-rocket
Adversarially review a grooming spec before implementation starts.
Compliance
wp-media/wp-rocket
Check a change against WordPress.org plugin rules and PHPCS standards.
Docs
wp-media/wp-rocket
Update developer-facing documentation to reflect code changes on the current branch.
Related
Questions about Issue Workflow
What does Issue Workflow do?
Work on a GitHub issue by number for wp-media/wp-rocket. An agent skill from wp-media/wp-rocket. Issue Workflow is an agent skill from wp-media/wp-rocket. Work on a GitHub issue by number for wp-media/wp-rocket.
How do I install Issue Workflow in Claude Code?
Run `npx skills add wp-media/wp-rocket --skill issue-workflow -a claude-code`. Or copy the skill folder (.claude/skills/issue-workflow in wp-media/wp-rocket) into .claude/skills/issue-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Issue Workflow in Codex?
Run `npx skills add wp-media/wp-rocket --skill issue-workflow -a codex`. Or copy the skill folder (.claude/skills/issue-workflow in wp-media/wp-rocket) into .agents/skills/issue-workflow in your project. Codex loads it when a task matches its description.
Can I use Issue Workflow 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 issue-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-workflow, .gemini/skills/issue-workflow, .github/skills/issue-workflow and .opencode/skills/issue-workflow in your project.
What does Issue Workflow need to run?
Going by SKILL.md and its folder, Issue Workflow needs a shell and JavaScript for the scripts in its folder and the command-line tools its instructions call (bash, git and gh). Our summary lists: Node.js; A Bash shell.
Does Issue Workflow access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue Workflow 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Issue Workflow use?
Issue Workflow 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 Issue Workflow use?
About 756 tokens (SKILL.md is roughly 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 Issue Workflow?
Skills that share tags, products or a category with Issue Workflow: Release Blog Drafter (obot-platform/obot, 1.1k stars), Release (jgravelle/jcodemunch-mcp, 2.7k stars), Keel (joseconti/declaracion-renta-espana, 190 stars) and Action Runner (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Workflow?
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.