Test WordPress Betas and RCs so your results mean something — and keep your own plugin or theme ahead of the next release. Guides, scripts, CI, and agent skills.
courtneyr-dev/wp-release-audit-method
Skill Claude CodeCodex
Hand off WordPress audit or testing work as ONE coworker-ready or SRE-ready markdown document, with privately-disclosed findings scrubbed to a bare acknowledgment. Use when asked to "hand off" a WordPress audit, make a handoff/shareable doc from testing findings, package audit results for a coworker/SRE/stakeholder…
courtneyr-dev/wp-release-audit-method
Skill Claude CodeCodex
Follow up after a WordPress release party — recheck filed tickets, retest what was resolved, run the full Phase 2 chain audit, check the fleet's distributed hosting-test participation, and draft (never submit) new issues, Trac tickets, or security reports. Trigger on "after the release party", "check my filed…
courtneyr-dev/wp-release-audit-method
Skill Claude CodeCodex
Run the release-day smoke sweep and produce the Slack-formatted test report. Trigger on "release party", "run the release day sweep", "wp release party", "test the RC and post results", or during a live WordPress release party.
courtneyr-dev/wp-release-audit-method
Skill Claude CodeCodex
Prepare WordPress Studio test environments before a release party, through control calibration. Trigger on "prep for the release party", "get environments ready", "wp release prep", "set up test sites for the beta/RC", or the day before a scheduled WordPress release.
courtneyr-dev/wp-release-audit-method
Skill Claude CodeCodex
Capture clean, Mac-faithful WordPress admin and front-end screenshots from a JSON brief, against any site you have credentials for. Trigger on "take screenshots", "capture the admin", "screenshot the site", or when a report or doc needs WordPress UI images.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: