Fix one bug. Review the diff.
Reproduce a broken contact link, ask Codex for one precise repair, and verify the actual diff and browser behavior.
Recording method: CLI file access was blocked. We attached real file contents to the prompt; Codex analyzed that supplied text. The recording tool then applied the reviewed one-line proposal and ran file, Git, Node and browser checks. This is an independent practice console, not the official Codex app UI. Processing waits are omitted. Voice is synthetic.
Choose your subtitle language in the player menu. Use fullscreen to inspect code; all explanations and practice prompts are also available in the localized lesson.
Translated transcript
0:00 · Define the repair
A good bug fix starts with a reproducible failure. We will repair one contact link, inspect the real Git difference, and check the result independently.
0:12 · Reproduce the failure
Click Contact. The address changes to contact-missing, but no matching section exists. The local verifier fails too. Preserve this failure before asking for a repair.
0:31 · Ask for one change
Local file access is unavailable in this CLI session. We attach real file contents and request a proposed diff. Codex analyzes the evidence; we will review and apply the repair separately.
0:46 · Read the actual result
Read the actual Codex report. Look for the cause, the changed line, and the check results. Browser checks that were not run must remain explicitly unverified.
1:03 · Review the diff
Review the proposed link change, then apply it with the practice button. The real Git diff shows one removed line and one added line. Independent verification passes; other files stay unchanged.
1:21 · Verify the visible fix
A passing script is only one layer of evidence. Test the real link with the mouse and keyboard. Narrow the viewport to three hundred ninety pixels and repeat the interaction.
1:40 · Repeat and record
Download a fresh bug lab. Capture the failure, request the smallest repair, then compare the diff and verify. Keep anything you did not test in the not-run section.
Recording evidence and limits
The evidence file contains the actual English prompt with supplied snapshots, Codex response, independent command outputs, file hashes and browser checks. It does not certify real-phone or Safari compatibility, fresh installation, or autonomous CLI file editing.
Download actual evidence · JSON