메뉴
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pr |
| description | INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment. |
Quick-reference for opening a PR. Full reference: docs/pull-request.md.
| Prefix | Use |
|---|---|
add/{feature} | New feature. |
update/{feature} | Iterating on an existing feature. |
fix/{bug} | Bug fix. |
try/{idea} | Experimental — open as draft. |
Reserved: release/{X.Y.Z} (owned by the release script), trunk.
git checkout trunk && git pull origin trunk
git checkout -b fix/something
Lint + tests must pass.
composer lint
npm run env-test
Changelog entry or Skip Changelog label.
composer changelog:add
Commit the entry on the same branch as the code change. End the message with punctuation. Write for end users — no class names, no internal jargon.
If neither a changelog entry nor a Skip Changelog label applies, stop and ask the user which they prefer. Don't open the PR with neither.
Code review. Delegate the diff to the code-review agent. Address every critical finding before opening the PR.
# Create PR (includes required assignment/reviewer).
gh pr create --assignee @me --reviewer Automattic/atmosphere
Copilot is requested as a reviewer automatically by the trunk branch ruleset — don't add it manually.
Use .github/PULL_REQUEST_TEMPLATE.md as-is — don't invent custom formatting. The body must include:
Write for end users; they appear in the WordPress update screen.
✅ Fix posts not appearing on Bluesky when published via Quick Edit.
✅ Add option to disable standard.site document records.
❌ Refactor Publisher class to handle edge case in applyWrites batch.
❌ Fix TID collision in transformer output.
End with punctuation. Never mention AI tools or coding assistants.
Read docs/pull-request.md when you need:
Type: prefix table).Development workflows for WordPress ATmosphere plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, or working with wp-env.
Testing patterns for PHPUnit tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ATmosphere features.
PHP coding standards and WordPress patterns for ATmosphere plugin. Use when writing PHP code, creating classes, implementing WordPress hooks, or structuring plugin files.
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.
MUST be invoked before creating any PR, pushing a branch for review, or running `gh pr create`. Covers changelog entries, branch naming, PHPCS/PHPUnit checks, and reviewer assignment.