القائمة
Update an existing skill or knowledge entry in phucbm/skills. Use when the user says "update my X skill", "update X knowledge", or "add this change to my X skill/knowledge".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Scaffold, revise and manage custom ACF Gutenberg blocks for WordPress with Tailwind CSS. Use when the user wants to create a new block, revise/audit blocks, or set up a WordPress blocks project.
Scaffold one or more ACF Gutenberg blocks from GitHub issues, a markdown brief, or interactive prompts. Generates block.json, fields.json, render.php, and optional view.js.
Discuss a new block's purpose and requirements with the user, then create a GitHub issue with a structured breakdown ready for /wp-acf-blocks:add-block.
Deep AI audit of all blocks or specific blocks — runs structural checks first, then uses AI to review content quality, descriptions, grammar, admin render justification, wrapper usage, and empty-state messages.
Fast structural audit of all blocks or specific blocks — checks required files, wrapper attributes, fields.json timestamp, previewImage, viewScript. No AI, runs instantly via script.
Set up a new WordPress theme with the wp-acf-blocks block development workflow
| name | update-skill |
| description | Update an existing skill or knowledge entry in phucbm/skills. Use when the user says "update my X skill", "update X knowledge", or "add this change to my X skill/knowledge". |
| allowed-tools | Bash Read Write Edit |
skills/<topic>/SKILL.md — thin wrapper. Update only if trigger wording, description, or knowledge pointers change.knowledge/<category>/<slug>.md — the actual content. This is usually what gets updated.Read the prompt — if arguments were passed with the slash command (e.g. /update-skill add the new retry logic to my groq skill), treat them as the user's description of what to update and proceed to step 1. If no arguments were given, ask: "Which skill or knowledge do you want to update, and what should change?" and wait for the answer before continuing.
Pull latest:
gh repo clone phucbm/skills /tmp/phucbm-skills 2>/dev/null || git -C /tmp/phucbm-skills pull
Surface related files — scan skills/ and knowledge/ for anything related to the topic. List all candidates and flag shared knowledge files:
"Files that may need updating:
skills/groq/SKILL.md(trigger description)knowledge/groq/streaming-integration.md(actual content — also referenced by skills/X) Should I update both, or just the knowledge file?"
Show a diff for each file that will change:
FILE: knowledge/groq/streaming-integration.md
CURRENT: <existing section>
PROPOSED: <updated section>
REASON: <why>
Wait for user confirmation before applying anything.
Apply edits, bump patch version in .claude-plugin/plugin.json, commit and push:
git -C /tmp/phucbm-skills add .
git -C /tmp/phucbm-skills commit -m "knowledge: update <topic>"
git -C /tmp/phucbm-skills push
Confirm the push URL to the user.
description is the primary trigger — keep it specific and slightly pushy; prefer surgical edits to stay under 500 lines.SKILL.md rarely needs updating — only if frontmatter description/when_to_use or knowledge pointers changeRead [\@/knowledge//.md`](/knowledge//.md) and apply...`Read and apply: followed by a bullet list of [@/knowledge/...](...) links