Prepare a clear change handoff

---
name: "aboutcodex-change-evidence"
description: "Turn a completed code or website change into an evidence-based handoff. Use when the user asks for a completion report, review summary, or a clear account of what changed and what was verified."
---

# Change evidence

Prepare a handoff from the actual change and the evidence available in the task.

Inspect the relevant diff or changed content when available. Identify the user-visible behavior before and after the change. Distinguish implementation facts from expected effects that were not measured.

For every claim that something was tested, locate the associated result. Record what ran, what it covered, and whether it passed, failed, or was blocked. Do not treat an unexecuted command or a test file's existence as a passing result.

Use references/NOTES.md to organize evidence. Select the details that help someone assess the change; avoid listing every tool call or reproducing noisy logs.

If a required check is still missing and can run within the user's authorized task, run it before finalizing. If it cannot run, explain the concrete limit. Do not widen the task into unrelated changes just to make the report look more complete.

Lead the handoff with the resulting behavior. Include material tradeoffs, unresolved failures, and a review link or relevant file location when available. Make deployment status explicit when it matters: local changes are not a public release.