Play-test your changes PhotoStructure released a `play-test` skill in its `coding` plugin that directs coding agents such as Claude Opus 5.5 high and Codex GPT-6.1 Sol xhigh to walk a developer through reproducing a reported bug or verifying a fix before merging, rather than testing against mocks and stubs. The skill sets up a starting state, asks the developer to confirm the setup, then issues steps like "click this" or "run this script" with an expected result, and includes a QR-code step for mobile browser testing. Developers install it via `/plugin marketplace add photostructure/coding-skills` and `/plugin install coding@photostructure` in Claude Code, or the equivalent `codex plugin marketplace add` and `codex plugin add` commands, then invoke `/coding:play-test` or `$coding:play-test`. Play-test your changes You’re staring at the PR from your coding agent, mouse poised over the merge button. CI is green. The changes seem reasonable. BUT. Will this database migration finish quickly on a larger database? Is this added field in the API going to break existing callers? Will those CSS edits cascade to way more than you expected? Will the frontend render consistently across browsers? And are the tests actually reproducing the issue your users reported, or are they testing a fiction composed of mocks https://en.wikipedia.org/wiki/Mock object and stubs https://en.wikipedia.org/wiki/Test stub ? What matters is whether it works for your users in production . In ye olden days , your QA team those 15 people over there, supporting 5 developers would spend a month building a test environment and writing a binder full of manual test cases. You’d toss a build over the wall and hear back the following week. I struggled to get that kind of help from agents. They’d either do everything behind the scenes without showing their work, or hand me the binder and make me do everything. I need to play-test these diffs At least in my experience with Claude Opus 5.5 high and Codex GPT-6.1 Sol xhigh, you say “ let’s play-test this ”, and they get it . For a reported bug, choose whether to reproduce it, verify the fix, or do both. For other changes, check the intended behavior. 1. They set up the starting state: files on disk, a half-imported library, or whatever the scenario needs. 2. They ask you to confirm that the setup matches what you want to test. 3. They say “click this” or “run this script” and explain what you should see. Read the script first to check that it does what you expect. 4. You report what happened, and together you check whether it matches the expected result. Pro tip: for mobile testing, ask your agent for a QR code linking to a URL your phone can reach. The skill below includes this step when you’re testing in a mobile browser. But in case they don’t get it, I added a play-test skill https://github.com/photostructure/coding-skills/blob/main/plugins/coding/skills/play-test/SKILL.md to PhotoStructure’s coding plugin that makes this explicit. In Claude Code , run: /plugin marketplace add photostructure/coding-skills /plugin install coding@photostructure For Codex , run these commands in your terminal: codex plugin marketplace add photostructure/coding-skills codex plugin add coding@photostructure Use /coding:play-test in Claude Code or $coding:play-test in Codex when you think everything’s pretty baked. You can play-test before a commit, alongside a gavel https://photostructure.com/gavel review, or while reviewing a pull request. From the hundreds of times I’ve used this with agents, I’ve seen the full spectrum of outcomes: - Holy crap, the agent nailed it . - Ah, most of the way there , but this UX needs polish. - Hmm, we need to address these two other scenarios I just discovered. - Oh dear, this is all quite wrong . Most of the time my play-testing reveals issues. Every bug I can fix before it bothers a user is a huge win.