Protocol

Review the file list before reading the agent's explanation

The diff knows what changed even when the summary forgets.

About 1 min read

Before you use it

Use when
  • The PR summary sounds plausible and pulls the reviewer toward the intended story.

Keep this limit in mind

  • Large generated changes may need specialized diff tooling, but they should not become invisible because review is inconvenient.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Start review with the complete changed-file list and diff statistics. Flag sensitive paths, deletions, lockfiles, test changes and generated files before reading the agent's narrative. Then evaluate whether the summary accounts for the actual change set.

Steps

  1. All changed files listed.
  2. Sensitive files highlighted.
  3. Deletions inspected.
  4. Tests and lockfiles inspected.
  5. PR summary checked against diff.
  6. Unexplained changes resolved.

An example

A PR description mentions an API fix, but the file list reveals a modified deployment script; review pivots before approval.

Check your result

The reviewer can account for every changed file independent of the agent's prose.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingReview the file list before reading the agent's explanation

Evidence and sources
Supports

OWASP recommends reviewing every file in an agent-generated change and flagging out-of-scope edits, especially lockfiles, CI configuration, tests and other sensitive files.

Automation can flag suspicious diffs but does not determine intent or correctness.

Secure Coding with AI Cheat Sheet · Out-of-Scope Edits and Review Anchoring

Supports

GitHub documentation says Copilot agent pull requests should receive the same thorough review as other contributions and warns reviewers to inspect workflow changes before allowing privileged Actions runs.

This is GitHub-specific implementation guidance; the general pattern is independent review before privileged execution.

Review output from Copilot · Review Copilot's changes; Manage GitHub Actions workflow runs

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details