| name | create-pr |
| description | End-to-end workflow for shipping a non-trivial feature or fix as a pull request in this repo — plan and get sign-off, implement, verify with PHPUnit/phpcs/build, verify manually in a real browser session, open a draft PR with a structured description, and triage/respond to review comments. Use when asked to implement something and open a PR, or to "ship" a change end-to-end. |
Create a PR
Phases in order — each catches something the previous one can't.
1. Plan
Skip only for trivial changes. Otherwise: read the closest existing
analogues in this repo and copy their pattern rather than inventing a new
one. Use AskUserQuestion for genuine open design forks, EnterPlanMode
for anything multi-file, and get explicit sign-off before writing code.
2. Implement
Match existing conventions file-by-file. Prefer narrow, purpose-built
capability/permission checks over broad grants (e.g. a role check or a
specific documented capability) — a broad grant tends to unlock more than
intended. php -l (or the language equivalent) after every edit.
3. Automated tests
docker exec wordcamporg-phpunit_wp-1 bash -lc 'cd /app && phpunit --testsuite "<suite name>"'
public_html/wp-content/mu-plugins/vendor/bin/phpcs <files>
public_html/wp-content/mu-plugins/vendor/bin/phpcbf <files>
cd public_html/wp-content/mu-plugins/<plugin>/ && npm run build
Check phpunit.xml.dist for the suite name covering the changed area, and
run the broader regression suite too before opening the PR.
