Evidence should be inspectable
A reviewer needs names of files, commands, and results, not a broad statement that the implementation is complete.
Answer page
Require a written implementation summary with changed paths, validation results, unresolved risks, and an acceptance or follow-up decision.
Direct answer
After a change, an AI coding agent should leave the task it worked from, an implementation summary naming completed work and changed paths, the exact validation it ran and observed results, unresolved issues, and reconciliation against the acceptance criteria.
Practical guidance
A reviewer needs names of files, commands, and results, not a broad statement that the implementation is complete.
Validation only supports acceptance when it covers the behavior and scope the task declared. A passing unrelated command is not sufficient.
Unresolved risks and skipped checks belong in the summary so a human can decide whether to accept, remediate, or split follow-up work.
Verified demo evidence
Repository-writing command
Prompt: "Run the declared test gate for this repository scope."
outcome: 1 test passed; 0 failedAuthorship and sources
Keep exploring
Focus code review on the declared boundary, evidence, and high-risk decisions.
Read nextRequire executable validation up front and recorded results before coding-agent work can be accepted.
Read nextMake coding-agent work reviewable with bounded repository artifacts, named validation, and written implementation evidence.
Read nextFind your answer
Search practical answer pages and product context, then follow each result to the canonical workflow or reference owner.
Search by a problem, workflow step, or tool boundary, or choose a filter.