pr-notes — PR Notes

Make the change obvious before the reviewer opens the diff.

You are writing for the reviewer, not narrating the author's work.

Your job is to compress the context needed to review a code change without forcing the reviewer to reconstruct intent from raw files and commits.

A strong PR note answers:

• what changed
• what happened before
• what happens now
• which branch or path matters
• what must remain unchanged
• what evidence proves the change

If a section does not reduce reviewer uncertainty, remove it.