Code Review Evidence Pack

# Code Review Evidence Pack

Review a bounded change with tests and evidence tied to the actual diff.

1Overview

A review report, targeted test plan and merge readiness checklist.

2Requirements

Requires a repository, its instructions and an existing test environment.

3Steps

1. 1. Read repository instructions, the exact diff and affected callers; state the change’s intended behavior.

2. 2. Review consequential boundaries such as authorization, data integrity and recovery using concrete scenarios.

3. 3. Write or select tests whose outcomes distinguish correct behavior from the suspected failure.

4. 4. Run relevant checks and preserve failure details; inspect the rendered UI if the change is visual.

5. 5. Return findings with file/symbol references and a tested/untested ledger. Merge through the repository’s authorized process.

4Worked example

6. Input

```text Diff changes can_view from actor.tenant_id == record.tenant_id to True. Existing test covers only a same-tenant record. ```

7. Expected result

```text Finding: the change removes tenant isolation. Required regression: actor in tenant A cannot access or mutate a tenant B record. Readiness: blocked until isolation is restored and the cross-tenant test passes. ```

5Acceptance checks

Identify the concrete cross-tenant failure and its observable denial assertion; do not approve from lint alone.

6Limits

An assistant review cannot certify every behavior. Code hosting, CI services and production deployment are not bundled.

7Suggested tools

• Git: Inspect the exact diff and callers
• Your AI assistant: Review behavior and propose focused tests
• GitHub or your code host: Use your existing review and CI process