Menu
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
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.
| name | release |
| description | Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases. |
Quick-reference for cutting a release. Full reference: docs/release-process.md.
npm run release
The script (bin/release.js) handles everything: changelog roll-up, version bump in atmosphere.php / readme.txt / package.json, readme.txt changelog mirror, unreleased marker replacement across *.php, optional Upgrade Notice prompt, then commits / pushes / opens a Release X.Y.Z PR.
Prerequisites: clean working tree, on trunk (or it'll switch you), gh CLI authenticated, at least one entry in .github/changelog/.
After the PR merges: draft the GitHub Release against trunk with the new tag.
The script doesn't handle these — patches are cherry-picked manually onto the previous release branch:
git fetch origin release/X.Y.0
git checkout release/X.Y.0
git cherry-pick -m 1 <merge-commit-hash>
composer changelog:write
# Update readme.txt changelog block, bump versions in atmosphere.php / readme.txt / package.json,
# replace any remaining `unreleased` markers.
git push origin release/X.Y.0
# Open PR against release/X.Y.0; draft GitHub Release with the new tag targeting that branch.
Full step-by-step: docs/release-process.md → Patch Releases.
composer changelog:add # Add one entry to .github/changelog/.
composer changelog:write # Roll up entries into CHANGELOG.md (script does this for you).
Required: end the message with punctuation, write for end users (no class names, no AI/assistant references).
✅ 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.
When adding a new public hook, deprecation, or _doing_it_wrong call, use the literal unreleased. The release script rewrites it:
/**
* @since unreleased
*/
\_deprecated_function( __FUNCTION__, 'unreleased', 'new_function' );
\apply_filters_deprecated( 'atmosphere_old_filter', array( $value ), 'unreleased', 'atmosphere_new_filter' );
\_doing_it_wrong( __METHOD__, \__( 'Use new_method().', 'atmosphere' ), 'unreleased' );
| Bump | When |
|---|---|
| Major (X.0.0) | Breaking public-hook signature changes, removed features, schema requires migration. |
| Minor (0.X.0) | New features, new public hooks, backward-compatible behaviour changes. |
| Patch (0.0.X) | Bug fixes only — no public hook changes. |
If any pending entry is marked Significance: major, the changelogger bumps to a new major version. Otherwise minor if any is minor, else patch.
Read docs/release-process.md when you need: