The professional loop
- Inspect nearby patterns and tests.
- Implement the smallest change that meets the goal.
- Run focused tests first, then broader checks.
- Review the diff and verify real behavior.
Implement the change. Then run the nearest test, lint, and build. For UI work, open the app and check the flow on mobile and desktop. Do not call the task complete while a verification is failing.
Tests with intent
Do not request coverage by habit. Ask for a test that would fail before the fix and protects important behavior such as permissions, empty states, network errors, limits, or accessibility.
Look at the UI
A successful build cannot detect clipped text, overlap, or confusing interaction. For visual changes, Codex should run the app, walk through the flow, and check representative viewport sizes.
Final evidence
The handoff should state what changed, which commands passed, and what could not be checked. A screenshot or test result is evidence; an unexecuted claim is not.
Lesson deliverable
What you will build
Practical evidence for "Implement, test, and review the interface" applied to a real or training repository.
Why it matters
The goal is to turn the lesson into a verifiable action, not just reading.
Starter repository or files
A small Git repository with Git, README, and one known validation command.
Steps
- 1. Inspect Git status before starting.
- 2. Ask Codex to work with limited scope.
- 3. Run the verification command.
- 4. Review the diff or produced evidence.
- 5. Record what is verified and what remains open.
Copy-ready Codex request
Apply the lesson "Implement, test, and review the interface" in this repository. Work in small changes, cite concrete files, run one verification, and finish with evidence and risks.
Expected result
A reviewable output: map, plan, diff, test, or report depending on the lesson.
Verification command
git status --short && git diff --stat
Manual check
Check that the result matches the requested scope and Codex did not touch unrelated files.
Mini exercise
Repeat the practice in another folder of the same repository, changing only one constraint.
Show solution
Keep the same goal, add one explicit constraint, and compare whether the final evidence improves.
Evidence to save
Save the prompt, commands run, relevant output, and git diff --stat.