القائمة
Create a pull request with proper branch, description, and labels
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
Generate a complete ability through an interview-driven workflow
Spin up a WordPress Playground instance with the plugin mounted and activated
Create a GitHub issue via interview — asks clarifying questions, inspects codebase, and files a well-structured issue
Scaffold a new ability with PHP backend, JS chat interface, and test case
Version bump, commit, push, and create GitHub release with notes
| name | pr |
| description | Create a pull request with proper branch, description, and labels |
| argument-hint | [base-branch] |
| allowed-tools | Bash(git *), Bash(gh *), Bash(npm *), Read, Grep |
If not already on a feature branch, create one from the commit history:
feature/<short-description>fix/<short-description>docs/<short-description>refactor/<short-description>npm test — unit tests must passnpx wp-scripts lint-js on changed JS filescomposer lint if PHP files changedgit diff main...HEAD to understand full scope of changesBase branch: $ARGUMENTS (default: main)
Use gh pr create with:
## Summary
<2-4 bullet points describing what changed and why>
## Changes
<list of files/areas affected>
## Testing
- [ ] Unit tests pass (`npm test`)
- [ ] Ability tests pass (`npm run test:abilities -- --file tests/abilities/core-abilities.test.js`)
- [ ] JS lint clean (`npm run lint:js`)
- [ ] PHP lint clean (`composer lint`)
- [ ] Manually tested in browser (if UI changes)
## Notes
<any migration steps, breaking changes, or reviewer guidance>
enhancement, bug, documentation, breaking-change-u flag before creating PRPrint the PR URL so the user can review it.