Give your coding agent a review checklist
https://patrickz.ai/learn/give-ai-a-review-checklist/

OUTCOME
Make a small code change with a review, meaningful test and rollback point.

YOU NEED
A coding agent, a small repository and version control. Work on a branch or disposable practice copy.

1. State the behavior
Describe a concrete before-and-after case. Identify the user action, expected response and boundaries. Ask the agent to inspect existing conventions before editing.

2. Review the proposed change
Request a file-level explanation and the reason for each change. Watch for unrelated rewrites, new dependencies and credentials in client code.

3. Test the failure that matters
Choose a test that would fail on the original bug or missing behavior. Include one ordinary case and one boundary. Run the project’s required checks.

4. Inspect and checkpoint
Read the diff, use the interface and record what was verified. Commit the scoped change so you can revert it. Keep untested behavior explicit.

PROMPT
Implement [specific behavior] in this repository. Inspect existing instructions and conventions first. Keep the change focused. Explain the diff, add or run a test that demonstrates the behavior, and report actual command results plus unverified limits. Never put secrets in browser code.

EXAMPLE / EXPERIMENT
A test that merely checks a button exists does not prove that saving survives reload. Test the user-visible outcome rather than mirroring the implementation.

CHECK YOUR RESULT
[ ] The diff matches the requested scope.
[ ] A meaningful behavior check passed.
[ ] A known checkpoint can restore the prior version.

IF IT FAILS
If a test passes without exercising the changed behavior, strengthen the assertion. If the agent reports tests it did not run, request actual output and inspect it.

MY RESULT / NEXT CHANGE