pr-plain-english-rewrite

Provide the existing PR title, body, and diff summary, then apply the rewrite rules: state what changes, what applies on merge, and what reviewers should check. The output uses a structured body with Why, What changes, non-goals, and reviewer focus sections.

A good PR title uses imperative mood like add, fix, or remove, names the changed thing rather than the internal journey, and follows the repo's convention such as type(scope): subject. Avoid vague titles like cleanup, improvements, or follow-up.

Yes, the same rewrite rules apply to PR comments, RFC summaries, design docs, and internal notes. For paste-ready PR comments, the outer suggested-body wrapper is omitted while keeping the same plain-English content.

The rewrite requires explicit bullets for database migrations, new or changed dependencies, auth or permission changes, public API or schema changes, destructive operations, feature flag changes, and configuration default changes. These must not be buried in prose.

Avoid it when the repo already uses specific terms as exact product or domain vocabulary, since cutting them would lose meaning. It also does not replace technical accuracy; necessary technical terms are kept and defined once rather than removed.