# Review the file list before reading the agent's explanation

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Review the file list before reading the agent's explanation

ID: MHC-D-RESEARCH-0657 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/review-the-file-list-before-reading-the-agent-s-explanation

The diff knows what changed even when the summary forgets.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- The PR summary sounds plausible and pulls the reviewer toward the intended story.

### Avoid when

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

### Explanation

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.

### Example

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

### Check

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

### Limits

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

### 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. — RS-1C68AE8325C384C0. Automation can flag suspicious diffs but does not determine intent or correctness. (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. — RS-AF6C3AA11CD6EA39. This is GitHub-specific implementation guidance; the general pattern is independent review before privileged execution. (Review Copilot's changes; Manage GitHub Actions workflow runs)
- RS-1C68AE8325C384C0: Secure Coding with AI Cheat Sheet — https://cheatsheetseries.owasp.org/cheatsheets/Secure_Coding_with_AI_Cheat_Sheet.html
- RS-AF6C3AA11CD6EA39: Review output from Copilot — https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/review-copilot-output

No review details supplied.
