Write code comments, PR descriptions, PR review replies, and other reader-facing prose so they describe the code as it is now — never the journey of how it got there, and never a transient PR/sibling-change reference. Use whenever writing or editing a code comment, a PR title/description/comment, or restating an issue. Triggers on adding/editing comments, opening or updating a PR, or replying to review feedback.
2026-06-24