review-for-reader

To pass the Stranger Test, review comments and docstrings as if you never saw the diff, then rewrite journal-style narration or stale references into self-contained, current-state phrasing that retains concrete values and intent.

Diff-anchored writing is prose in comments or docs that only makes sense to someone holding the diff, referencing removed code or temporal changes. It creates stale documentation that fails to explain the current state to future maintainers who lack historical context.

Review a PR for stale comments by applying a fresh-context reviewer paradigm that surfaces references to removed code, journal-style history, and what-not-why explanations, then rewriting the flagged prose to current-state phrasing while preserving durable rationale.

This prose review approach focuses exclusively on documentation, comments, docstrings, README files, and PR descriptions. It does not evaluate code logic, instead targeting diff-anchored writing and stale references to ensure explanations remain meaningful without historical context.

Avoid diff-anchored prose rewriting when you need to review code logic, enforce architectural patterns, or validate functional behavior. This approach targets only temporal framing and stale references in documentation, preserving concrete values rather than assessing runtime correctness.