How to use Codex to prepare WordPress plugin releases
The author reports replacing a careful five-minute release ritual with one command and a diff review.
dev.to
Original prompt
Shared by the source author. See source notes for context.
bump this plugin's version from 1.0.9.10 to 1.0.9.11. Change two places: the Version: header in the main PHP file and the Stable tag in readme.txt. Change nothing else.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- rapls
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports replacing a careful five-minute release ritual with one command and a diff review.
- Human involvement
- The author confirms the version diff and reads git diff before anything ships.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Configured Codex and stored project conventions in AGENTS.md.
- Asked codex exec to update the PHP header and readme Stable tag.
- Wrapped version updates and changelog drafting in a release script.
The author uses Claude Code and Codex side by side while building WordPress plugins. Claude Code handles exploratory conversations and design, while Codex's non-interactive mode handles repeatable work that can be called from a script. The release example focuses on two version fields that must agree: the main PHP file's Version header and readme.txt's Stable tag.
They configured Codex with a model and reasoning setting, kept project conventions in AGENTS.md, and used codex exec for bounded instructions. One command asks for a version bump in those two locations and explicitly excludes other changes. The author describes checking the proposed diff to confirm the edits match the request.
They then wrapped release preparation in a shell script. It accepts a new version, asks Codex to update the version fields, and asks it to add a changelog section from recent commits using the existing format. The script ends with git diff, which the author reads before shipping. They report that a careful five-minute ritual became one command and a diff review.
Who it's for: WordPress plugin maintainers with recurring release chores and a willingness to inspect generated changes.
Prompt
Original prompt
Source: dev.to · rapls
Frequently asked questions
Which version fields did Codex change?
The main PHP file’s Version header and the Stable tag in readme.txt.
How did the author review release changes?
The author describes confirming the two version edits and reading git diff at the end of the release script before shipping.
More details
Remaining steps
- Read the resulting git diff before shipping.
About this account
Codex performs bounded version edits and changelog drafting through non-interactive script calls.
Platform: dev.to. Attribution: https://dev.to/rapls/i-run-claude-code-and-codex-side-by-side-heres-the-division-of-labor-that-actually-works-4hkg. Prompt: Original (quoted from source). Sourced by the Agents In Use pipeline.
Credit: rapls on dev.to
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex CLI · Git · Bash · WordPress
WordPress · Release automation · Changelogs
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.