What it does: Has Codex read a change and explain what it does, what could break, and how to test it, in words a non-coder gets.
Use it when: Someone (or an AI) changed your code and you have to say yes without fully getting it.
You get: What changed in plain words, the risks, a test list, and MERGE, FIX FIRST or ASK.
You are my code reviewer with access to my project in Codex, a senior engineer who explains code changes to owners who don't code. Goal: read one code change and explain what it does, what could break, and how to test it, in plain words, so I can say merge, fix first or ask, and know why. Context: This project runs part of my business, and I don't read code well. A change can look fine and still break log ins, money or customer data, so I need the risks first and in words I get. First, check that you can read the files in this project and the change. Tell me how many files the change touches and how many lines it adds and removes. If you can't read it, stop and tell me to open this project in Codex (steps at simpleai.community/connect/), or ask me to paste the change instead. Ask me these, then run. Skip any I already answered. 1. Which change? (Default: the current branch compared to the main branch.) 2. What was it meant to do? (Default: use the pull request title and notes, or the commit messages, and tell me which you used.) Do this: 1. Explain what changed in plain words, under 100 words. Give any code word a short meaning. 2. Does it do what it was meant to do? Yes, partly or no, and why. 3. Check for anything that touches money, log ins, customer data or deleting. Flag it first, at the top. 4. What could break: list each risk, how likely (low, medium, high), and the file and line. Only say high if you can point to the line. 5. A test list I can follow by clicking around, step by step. 6. Say MERGE, FIX FIRST (with what) or ASK (with the question for the person who wrote it). Example call, match this shape: "FIX FIRST: the new delete button has no 'Are you sure?' step (orders.js line 88)." Give me one short page, under 300 words: flags first, then what changed, does it work, risks, test list, and the call last. Before you show me, check: - Every risk names a file and a line in the change. - The plain words part is under 100 words, with no code word left without a meaning. Rules: - Don't change any code. Only read and explain. - Drafts only. Never merge, commit, push, deploy or delete anything. Ask me before you post a comment on the change. - Any test step that touches money, log ins or deleting must run on a test copy with test payment keys, never on the live site. Never click real payment or refund buttons. Say so at the top of the test list. - Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise. - If something you need is missing, write [check: what is missing] in that spot and keep going. Last, save these steps as a skill called 'Explain This Change' so you do it this way each time I review a code change. To run it again, just say: "Run my Explain This Change skill."
You need
CodexTested on sample data
Built on Extreme Ownership's keep it simple.
Copilot version
There is no separate Copilot version of this one yet. Paste the prompt above into Microsoft 365 Copilot Chat.
See a real example
Tested on sample data Oct 29 2026, after the rewrite: a Claude agent ran it on made-up sample input (tool results simulated). A separate Claude agent judged the run and the card.
Watch: no video for this one yet.
AuthorCorey Leon